RESULT_CODE_HUNG when logging in as user (Evo skin)

[RogierMaas]

Hi all,

My panels are accessible behind a proxy which forwards panel.domainname to localhost:2222. Since a few weeks, some users cannot seem to get past the login page (Chrome says: aww, snap and "Error code: RESULT_CODE_HUNG") while some users cannot get to their own panel.theirdomainname at all. It just shows the animated DA-logo. So something is loading, but not the login page.

I've searched and searched but I'm not able to find the answer anywhere..

Thanks!

 

[RogierMaas]

Also... when logging in as Admin, there seem to be no installed widgets. Might this have to do with the mentioned problem..?

 

[RogierMaas]

DA is being proxied through Apache but the referrer seems to be off:

/var/log/directadmin/error.log:
2024:03:20-13:44:48: Referer host does not match panel.mydomain.tld != panel.mydomain.tld:2222
2024:03:20-13:44:49: Referer host does not match panel.mydomain.tld != installatron.com
2024:03:20-13:44:49: Referer check failed for 12.34.56.78

The second I get: mydomain.tld is not installatron.com...

Apache config:

<VirtualHost |IP|:|PORT_443| |MULTI_IP|>
ServerName panel.|DOMAIN|
ServerAdmin |ADMIN|

SSLEngine on
SSLCertificateFile |CERT|
SSLCertificateKeyFile |KEY|
|CAROOT|

#ProxyRequests off
SSLProxyEngine on
ProxyPass / https://|DOMAIN|:2222/
ProxyPassReverse / https://|DOMAIN|:2222/
ProxyPreserveHost On

CustomLog /var/log/httpd/domains/|DOMAIN|.bytes bytes
CustomLog /var/log/httpd/domains/|DOMAIN|.log combined
ErrorLog /var/log/httpd/domains/|DOMAIN|.error.log

 

[Richard G]

I don't know really what could be going on. But maybe it's easier to make DA accessible via port 80?

Accessing DirectAdmin Panel | Directadmin Docs

DirectAdmin Knowledge Base

docs.directadmin.com

 

[RogierMaas]

I don't know really what could be going on. But maybe it's easier to make DA accessible via port 80?

Accessing DirectAdmin Panel | Directadmin Docs

DirectAdmin Knowledge Base

docs.directadmin.com

That's exactly what I already have.. I have used 'panel' as hostname in every user-domain and it proxies requests for that hostname to localhost:2222 or |DOMAIN|:2222 (nothing seems to be really working)

 

[Richard G]

That's exactly what I already have..

Oh... Because I can't find this back in the manual.

Apache config:

<VirtualHost |IP|:|PORT_443| |MULTI_IP|>
ServerName panel.|DOMAIN|
ServerAdmin |ADMIN|

also in the proxypass, I don't see

ProxyPass / https://|DOMAIN|:2222/

but I see:
ProxyPass / "https://server.example.com:2222/"
because in the example you need to fill in the server's hostname, not the domain name.
However, it's odd that it worked before.

I presume you also seperately created a panel.domain.com as a full domain and not subdomain

I wonder what the installatron.com referrer is doing in the error message too.

I don't work/understand proxy's so I might be totally wrong.

@Active8 any clue?

 

[RogierMaas]

Well, I have replaced a few values. DA will replace |DOMAIN| with whatever the users' domain names are. The ProxyPass directives would be exactly the same when parsed. This has always worked (since 2014 or so) using https://127.0.0.1:2222/ as hostname for the ProxyPass. The only difference is that this 'panel'-website is in every users' own DNS and httpd config. This doesn't work without ProxyPreserveHost On, not sure why...