We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 26922
    • 3 Posts
    Hello,

    I have an addon domain under primarydomain.com/modx

    if I go to www.addondomain.com, it shows me the page.
    But any inner pages created by modx, returns a 500 error or a 404 error.
    If I just have flat html files or something, I can get to those directories.

    I enabled friendly URL’s in the addon domain. Could this be causing the issue?
    I’ve spent several hours trying different htaccess combinations to no avail.

    Does anyone know of the exact htaccess I should have in both the primarydomain and the addondomain?
    Is this even possible with friendly URL’s turned on in modx for both sites?

    Thanks for any information!

    Shao
      • 30107
      • 44 Posts
      Sounds to me that you want to use modx in combination with two different domains. Maybe the following thread could be interesting to you: http://modxcms.com/forums/index.php/topic,35543.0.html
        • 26922
        • 3 Posts
        Apologies, I should have been more clear.

        The solution in the link above seems to apply to running several domains from a single modx installation.

        In my case I have two domain names pointing to one shared server account and running two seperate modx installations. So at the moment the modx files for primarydomain.com are installed in the root directory while addondomain.com modx files exists in a /modx subdirectory. addondomain.com points to primarydomain.com/modx.

        The problem is as follows: Going to primarydomain.com/modx/blog.html, for example, loads the page correctly, however, addondomain.com/blog.html shows a 500 Internal Server Error.

        I suspect the issue is with the default rewrite rules in the /modx/.htaccess file. Deleting the file and disabling friendly URLs in modx config allows the addondomain.com site to work correctly.

        Any insight would be vastly appreciated. Someone on IRC suggested that addon domain rules as created by cPanel might be creating a conflict, but was unable to offer a solution.