giving 500 error?

Well-Known Member
Mar 24, 2002
Not sure if there's something wrong here or what but before I (and clients) could use:
... and it would redirect to the appropriate socket and URL for the webmail landing page.

Now though it hits a 500 error page.

Having noted a few other threads I've checked and found that: is being redirected properly and the landing page is there if you go to the socket page.

It's just the old style approach that is just refusing to work.

Any ideas as to what could be causing this or if something has been deprecated?

... and yes I've upcp --force already... No change..