From the logs it looks like a configuration issue. You set up Wings with a url containing https but you aren't using encryption. Change it to http
#unRAID - Panel & Node on same system. (Same Network). Unable to connect Node to Panel.
gray gust
https://<IPHERE>:8001/api/remote/servers?page=0&per_page=50": http: server gave HTTP response to HTTPS client
tender sentinel
Let me try this, as I believe it was HTTP prior to me changing it. I'll respond here once I've done it.
gray gust
That looks like it's working now, status 200 means ok.
Since there are no errors in wings, check your browser console for errors if you're still getting the red heart.
tender sentinel
Browser console for Panel? Or Wings? If I open Daemon (Assuming this is Wings), it instantly closes the log window.
gray gust
Browser console for Panel? Or Wings? If I open Daemon (Assuming this is Wings), ...
On the page with the red hearts in your browser
Your browser will be communicating with wings
tender sentinel
When you state that, is that the thing I seen in another thread I read? F12. Should show an error or something?
tender sentinel
How would I determine what the error is from Console? Let me see what I can see. Thank you for having patience with me by the way...I apologize for this.
ASH
I see it now
mild sundialBOT
I have found the following for: https://media.discordapp.net/attachments/1102098889152139344/1102108021099872257/image.png
The domain you are trying to reach does not have valid DNS records or the DNS cache of your machine has not been updated yet. You can use https://dnschecker.org/ to verify the DNS records of a domain.
tender sentinel
Since I am using duckdns, I am assuming I will need to use something else because of this.
gray gust
duckdns should work. Is this on your home network or a VPS? (Wings)
tender sentinel
Its both on the same system, Unraid. Was under the thought that I could host both on the same machine so I do not need to either make another server just to host the panel/wings or pay for one.
Home Network*
Verifying the DNS Records. I type that DNS in and everything has a green checkmark.
gray gust
Yes, they can both be on the same machine. From your Desktop where your running the web browser you get this error on, check if the FQDN you put for wings along with the demon port is accessible. I recommend nmap
tender sentinel
I'm not running a browser within Unraid/Linux. I am using Chrome to access a GUI for it. Will that matter?
Installing nmap now to check.
This will take a while because I know nothing of what this is. So when I figure this out I will respond here.
tender sentinel
Yes, they can both be on the same machine. From your Desktop where your running ...
When you say accessible - this just means it needs to be able to be used to access something correct? I can use it to access something, so it should mean it works. As for the port, I will (assume) the port works since I have it port forwarded the same way the rest of the ports on the server are port forwarded.
I responded with this as I feel this is going to take me quite some time to figure out, in hopes my limited knowledge can supply an answer. Should I try a different misc port for the Daemon?
gray gust
It's open, so the firewall is ruled out as an issue.
@tender sentinel Going off your wings logs your daemon port is 8001, but going off the image you sent, your browser logs, your browser is trying to connect to port 8080, the default. If it really is set to 8001 try it in a new private tab so you don't have to worry about cache, and check your panel database to see what port the panel is trying to connect to. You may have port 8080 set as daemon under node in your panel, but 8001 in the wings config.
If they both say 8001 and you get the same error in a private tab, you need to go into your panel database and edit the port from 8080 to 8001.
tender sentinel
(Been changing stuff around to try to fix things, this is what it is at now. Will try a private tab, one moment.