Unable to access control panel after upgrade to 1.2.2

  • After disabling my plugin, all is working fine again? No redirect (301) to another domain?

  • That faulty redirection was active since I've updated from 1.1.5 to 1.2.2.
    I was suggested to fix that with installing the PanelRedirect plugin. After activating the plugin the issue wasn't fixed, so deinstalling the plugin again won't fix the problem either.


    Tried this and still:


    https://hosting.fqdn.tld:443 is 301 redirected to http://customerX.tld:80
    http://hosting.fqdn.tld:80 is 301 redirected to http://sub.customerY.tld:80


  • Please show us the content of the customer1-domain.tld_ssl.conf.
    PS: I really think that you have some own config files (due the 301 redirect). You could purge apache2 (removes all configs) and rerun the installer (should be the easiest way).

  • @lorus


    This is not a faulty redirection and more, this is not a redirection at all. This is the expected Apache behavior. Your "hosting" domain is now available through nginx on specific ports. Thus, if you try to access it through common ports (80/443), which are served by apache, Apache will serve the content of the first virtualhost found which will not be your hosting domain because he doesn't know about it (no virtualhost for it).


    Here, you must install the PanelRedirect plugin to proxy the requests for your hosting domain made on ports 80/443 to nginx on specific ports.

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

  • Here, you must install the PanelRedirect plugin to proxy the requests for your hosting domain made on ports 80/443 to nginx on specific ports.


    This is exactly what I've tried, but the plugin doesn't resolves the issue. I've tried to describe this in Post 33390 with as much information I was able to gather


    I've no further idea, so I would be very thankful if you could help me digging deeper.

  • Please show us the content of the customer1-domain.tld_ssl.conf.
    PS: I really think that you have some own config files (due the 301 redirect). You could purge apache2 (removes all configs) and rerun the installer (should be the easiest way).

  • You could purge apache2 (removes all configs) and rerun the installer (should be the easiest way).


    That did the trick. Thanks @Ninos for requoting. Can't believe that I completly missed that post. Sorry for that stupidness :-/


    Thanks for assisting and keep up your good work :-)

  • Np
    PS: Next time please create your own thread, because this problems were not similar..