#504 when panel tries to access /admin/nodes/view/2/system-information
16 messages · Page 1 of 1 (latest)
but it 504s when the panel itself? when i open it manually i get a 404 page
the node is just node1.panel.domain.com with the panel being panel.domain.com
the node is directly forwarded (DMZ with ufw) but the panel is nginx proxy passing to apache2 internally (weird setup but its all i could get working)
all ran on the same machine, the only thing im thinking it could be is that the panel is trying to hit panel.domain.com on the backend which wouldnt work because anything on the network cant access the public IP (from the DMZ)
the node is set to access the panel from localhost, hitting apache2 directly (which works fine) since it cant access the domain (cant hit its own public IP)
forgot i had this
how can i get past this behavior?
i need a way for the panel to make internal requests to the node through localhost, but still have it listed publicly under the real domain
because now my browser cant access it because its being told to look for it under localhost
okay so i assumed this wasnt gonna work and i just did the best workaround i could
for anyone in the future, on *nix based OS's: edit /etc/hosts and add lines like this
put your domain there, and any outboud traffic thats supposed to go to there: will go back to localhost