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.
#Wings: dial tcp 81.16.214.169:443: connect: connection refused
proud doveBOT
spiral pilot
I want Wings to connect to pterodactyl.example.com:443, not 81.16.214.169:443.
This happened after updating my Wings version, so I tried going back a few versions and it actually worked there like a charm. But I want to run on the newest Wings version of course. What would I need to change?
spiral pilot
Instead it should access on the actual domain, which working just fine here:
opaque dome
You tried to access a https port using http. That response is expected. You also put the port twice.
opaque dome
I want Wings to connect to pterodactyl.example.com:443, not 81.16.214.169:443.
...
As you can see from your error message, it already is attempting to connect to pterodactyl.example.com
spiral pilot
You tried to access a https port using http. That response is expected. You also...
I just added the port twice for clarification purposes.
spiral pilot
As you can see from your error message, it already is attempting to connect to `...
Yes, and how do I fix this? My panel is running on HTTPS, my Wings Client is using Standalone Certificates from Let's Encrypt. Did I miss something?
opaque dome
Adding a port twice doesn't clarify anything...
is 81.16.214.169 the correct IP address for pterodactyl.example.com?
spiral pilot
is `81.16.214.169` the correct IP address for `pterodactyl.example.com`?
Yes, it is. (Just an example one though.)
opaque dome
Well you will need to find out what is blocking connections from your wings server to your panel server
spiral pilot
Well you will need to find out what is blocking connections from your wings serv...
So is the Wings Server blocking the connection or the panel server?
opaque dome
from your wings server to your panel server
Only you know your network.
Could be blocked anywhere along the way
spiral pilot
Sorry, I just needed clarification. Maybe it's because I didn't correctly setup the NAT to my Wings server. Thanks for you help, I'll have a look on that.
spiral pilot
```from your wings server to your panel server```
Okay, I had a look and everything looks fine.
I also reverted back to Version 1.6.2 of Wings and it worked completely fine there. What's my issue here? I don't see. The firewall has port 443 open (I wouldn't be able to access it via the browser) and Wings only exposes port 8080 after it could successfully connect to the panel, which it obviously didn't. I had a look through the Wings commit and might suspect that this happened after upgrading the TCP Dependency.