I have the panel and node setup in separate VMs on the same machine.
SSL enabled for both.
Using dynamic DNS to route traffic to my network.
I have port forwarding for all ports.
nodes list has red heartbeat.
If I use a local IP in the etc/hosts file to the node, it somewhat works. But still can't access console or get the heart beat to be green.
#Panel is having troubles communicating node
64 messages · Page 1 of 1 (latest)
Make sure that your wings are running using systemctl status wings and that your Wings ports (by default 8080/2022) are open in your firewall or router. This website can check your ports https://dnschecker.org/port-scanner.php
Browser console errors can also provide additional debugging information. More troubleshooting steps can be found at https://pterodactyl.io/panel/1.0/troubleshooting.html#cannot-connect-to-server-errors
Should the panel and wings be located on the same network, you might experience NAT reflection issues. In that case, type .nat for more information.
Suppose you are having trouble connecting to a Panel or Node on the same network as your device, or Panel and Wings can't reach each other on the same network. In that case, you may have to edit your /etc/hosts file to point the domain to the local IP, as some routers don't handle NAT Loopback correctly, if at all. On Windows, this file is at C:\Windows\System32\Drivers\etc\hosts
192.168.1.24 panel.mydomain.com node1.mydomain.com
192.168.1.25 node2.mydomain.com
This allows me to see node information but still fails on the console and health check.
Get "https://panel.jayrivers.info:8444/api/remote/servers?page=0&per_page=50": context deadline exceeded (Client.Timeout exceeded while awaiting headers) http: request creation failed github.com/pterodactyl/wings/remote.(*client).request.func1 github.com/pterodactyl/wings/remote/http.go:151 github.com/cenkalti/backoff/v4.RetryNotifyWithTimer.func1 github.com/cenkalti/backoff/v4@v4.2.1/retry.go:18 github.com/cenkalti/backoff/v4.doRetryNotify[...] github.com/cenkalti/backoff/v4@v4.2.1/retry.go:88 github.com/cenkalti/backoff/v4.RetryNotifyWithTimer github.com/cenkalti/backoff/v4@v4.2.1/retry.go:61 github.com/cenkalti/backoff/v4.RetryNotify github.com/cenkalti/backoff/v4@v4.2.1/retry.go:49 github.com/cenkalti/backoff/v4.Retry github.com/cenkalti/backoff/v4@v4.2.1/retry.go:38 github.com/pterodactyl/wings/remote.(*client).request github.com/pterodactyl/wings/remote/http.go:136 github.com/pterodactyl/wings/remote.(*client).Get github.com/pterodactyl/wings/remote/http.go:81 github.com/pterodactyl/wings/remote.(*client).getServersPaged github.com/pterodactyl/wings/remote/servers.go:201 github.com/pterodactyl/wings/remote.(*client).GetServers github.com/pterodactyl/wings/remote/servers.go:26 github.com/pterodactyl/wings/server.(*Manager).init github.com/pterodactyl/wings/server/manager.go:235 github.com/pterodactyl/wings/server.NewManager github.com/pterodactyl/wings/server/manager.go:36 github.com/pterodactyl/wings/cmd.rootCmdRun github.com/pterodactyl/wings/cmd/root.go:138 github.com/spf13/cobra.(*Command).execute github.com/spf13/cobra@v1.7.0/command.go:944 github.com/spf13/cobra.(*Command).ExecuteC github.com/spf13/cobra@v1.7.0/command.go:1068 github.com/spf13/cobra.(*Command).Execute github.com/spf13/cobra@v1.7.0/command.go:992 github.com/pterodactyl/wings/cmd.Execute github.com/pterodactyl/wings/cmd/root.go:71 main.main github.com/pterodactyl/wings/wings.go:17 runtime.main runtime/proc.go:250 runtime.goexit runtime/asm_amd64.s:1598
There were too many logs to read @slender arrow. Please post 5 or less. Alternatively, please share larger logs using paste sites, such as pteropaste or hastebin.
Get "https://panel.jayrivers.info:8444/api/remote/servers?page=0&per_page=50": context deadline exceeded (Client.Timeout exceeded while awaiting headers) http: request creation failed
@slender arrow; It looks like the Panel or Wings is responding too slowly, causing the request to timeout. Usually, this indicates some sort of a network issue.
Should the panel and wings be located on the same network, you might experience NAT reflection issues. In that case, type .nat for more information.
Curl works from panel to node, but still can't get the green heart
No errors logged in wings --debug
proxmox is the hypervisor
I mean if curl works, its unlikely to be a nat loopback issue
Port forwarded, firewall all ok?
Maybe the culprit is the network you share using the VM?
Honestly not much experience running them in vms
It was all working with http, as soon as I swapped out to SSL things got wonky
You'll need to grab error logs for Wings and share the link with us. The following command will help you collect the required information for debugging: sudo wings diagnostics
Also, what does the browser console say?
8080
And the panel uses 8444?
yes
You'll need to grab error logs for Wings and share the link with us. The following command will help you collect the required information for debugging: sudo wings diagnostics
I have found the following for: https://ptero.co/hozyjicyja
You already have an instance of Wings running through systemd service and are trying to start another duplicate instance, for example by using the commands wings and wings --debug, or another service is using the port.
Use ss -plnt | grep :8080 (or grep :8443 depending on the port) to find what process is currently running and stop it. You can type killall wings to shutdown any ghost Wings process.
This is for the console
This for nodes list
So definitely something wrong with 8080
Yea for sure
Suppose you are having trouble connecting to a Panel or Node on the same network as your device, or Panel and Wings can't reach each other on the same network. In that case, you may have to edit your /etc/hosts file to point the domain to the local IP, as some routers don't handle NAT Loopback correctly, if at all. On Windows, this file is at C:\Windows\System32\Drivers\etc\hosts
192.168.1.24 panel.mydomain.com node1.mydomain.com
192.168.1.25 node2.mydomain.com
Yes, and I can curl it from the panel VM
Let me try moving to a different port. Maybe ISP doesn't allow 8080
Worth a shot
still no luck
Hmm, odd
Not after changing the ports
Ahhh
I think it's all good now!
Glad
Thanks for your help!
Np