#443 connection refused (Single IP, 2 servers)

33 messages · Page 1 of 1 (latest)

dusk void
#

Can anyone help me?

I get this error in de wings debug:
dial tcp ip:443: connect: connection refused

But the panel is reachable from 443 but I have split the Pterodactyl installation between a web server and a server for wings and docker. Ports 80 and 443 refer to the web server and ports 8080, 8443 and 2022 refer to the server running wings and docker and the ports are open in the firewall.

I have also installed and started wings on the wings server but do **not **see any process running on port 8080 or 8443 while wings is active (systemctl status wings). So when I run the auto deploy command, I get the dial tcp ip:443: connect: connection refused error. The reset command doesn't work.

wraith peakBOT
#

Please explain the issue you're experiencing in as much detail as possible. Preferably with error messages in a text format or paste link to logs. Nobody can assist you without information that helps to understand the issue. Help us help you. Messages such as "doesn't work" or "i need help" will most likely be ignored.

dusk void
#

I did broski

proud berry
#

check if those ports are open

dusk void
#

If on the server itself the ports are not found, the tests also fail.

proud berry
#

timedout means those ports are closed on your device

#

Use:
sudo ufw allow <the port you want to open command

#

in your example

dusk void
#

If I enter an unknown port, I also get a timeout. The ports are not active on the server on which wings is (actively) running, that's the problem, isn't it?

proud berry
#

sudo ufw allow 2022

#

sudo ufw allow 8080

dusk void
#

The ufw firewall is inactive so it cannot block ports then.

proud berry
#

sudo ufw allow 8443

#

just run the commands 🙂

#

I had the same problem

dusk void
proud berry
#

if you check again here

#

are they still timed out?

dusk void
#

yes

proud berry
#

sad

#

sorry I couldn't hlep

verbal void
dusk void
# verbal void send the screenshot of node settings Provide the panel link

I think I found sth, I runned the curl cmd on the web server and on the wings server for the panel domainname and on another domainname that points to the server (for port 80 and 443) and I got:
curl: (7) Failed to connect to *domain* port 80 after 6 ms: Connection refused
curl: (7) Failed to connect to *domain* port 443 after 6 ms: Connection refused

verbal void
#

the issue is resolved ?

dusk void
#

no

#

That is part of the problem.

#

The connection refused