Sorry if duplicate, posted in wings help earlier:
I'm currently having issues accessing wings from my panel, getting a red heart and console logs report "connection refused". I have adjusted my hosts files on both the node and panel servers. I have confirmed that both the node and panel servers can reach each other and are correctly resolving each other's FQDN to their corresponding IPs. Upon trying to curl the node's daemon port from any machine on my network I get no response even when using the IP itself instead of the FQDN. I created a test node on a different server to verify it wasn't an issue with the VM itself and am getting the same issue. Here are the wings logs, https://ptero.co/orowygadul I also have verified UFW or any firewall rules are not enabled.
#Error accessing node
vagrant patrol
ornate fossilBOT
I have found the following for: https://ptero.co/orowygadul
@vagrant patrol; 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.
vagrant patrol
Have tried the above nat steps.
agile geyser
Keep in mind, heart color and console are your BROWSER connecting to wings
.nat would apply to your PC, if all on the same network
vagrant patrol
I currently have two other working nodes that are correctly connecting on my main PC without needing hosts entries. I also have tried to curl from the panel to ensure that it also is not reachable from there.
I added a host entry to resolve the FQDN to test if that changes but it now shows no console errors and still does not connect.
agile geyser
From your pc:
Can you ping your node local IP
Can you ping your node FQDN
Can you curl the node FQDN:port
From your node:
Can you ping your panel local IP
Can you ping your panel FQDN
Can you curl the node FQDN:port
vagrant patrol
I am unable to curl the node from my pc and unable to curl from the node itself, "Couldn't connect to server"
agile geyser
What's the full response?
vagrant patrol
Failed to connect to 192.168.0.6 port 8043 after 0 ms: Couldn't connect to server.
From pc it simply gives no response.
agile geyser
8043?
Your logs say you're using 8020
vagrant patrol
Ah apologies, I had updated both the panel and config.yml to reflect the port change
But with earlier testing using port 8020, it still gave the same response. Here are current logs https://ptero.co/awitihiwib
ornate fossilBOT
I have found the following for: https://ptero.co/awitihiwib
@vagrant patrol; 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.
agile geyser
Oh wait
my bad
Curl your panel from your node
vagrant patrol
Any specific port I should try to curl?
agile geyser
Whatever port your webserver is on
agile geyser
Anything in panel logs perchance?
vagrant patrol
The node im testing is bigmine, not the test one. That one can be ignored, was testing an identical setup on a different server.
I see an error with the connection timing out when attempting to connect to the node, not sure if anything else is present.
agile geyser
Right, now try curling https://bigmine.pog-smp.xyz:8043 from your panel
vagrant patrol
The curl appears to hang, no response.
vagrant patrol
I am able to ping from the panel using both.
agile geyser
That pretty much rules out routing then
Double, absolutely, 100% check there's no firewall at play