Auto-Deploy my Node via the token

[stoic wasp]

Hey I get the error while trying to Auto-Deploy my Node via the token
-Type:[application/json]] jopanel.duckdns.org/api/application/nodes1/configurationFailed to fetch configuration form the panel.
Get "jopanel.duckdns.org/api/application/nodes/1/configuration": unsupported protocol scheme ""

In the .env I have http:// before jopanel.duckdns.org

[narrow cosmos]

@stoic wasp You are missing a protocol scheme from the URL. Make sure your Panel URL contains https://or http:// in the .env and Wings config.

[stoic wasp]

I did that but the Wings config is empty what am I supposed to edit/write there?

[stoic wasp]

I just copyed the node code block there not and Im trying to start the wing but no luck. Here is the log https://pastebin.com/4TdBWb7V

[narrow cosmos]

I have found the following for: https://pastebin.com/4TdBWb7V
@stoic wasp You'll need to grab error logs from Wings. The following command allows to easily collect the relevant data and share the link with us: sudo wings diagnostics

[stoic wasp]

here you go https://ptero.co/ajalybarin

[narrow cosmos]

I have found the following for: https://ptero.co/ajalybarin
@stoic wasp; Wings must have a certificate to use when SSL is enabled. Follow this guide to learn how to generate SSL certificates: https://pterodactyl.io/tutorials/creating_ssl_certificates.html

[stoic wasp]

Can somebody guide me thought that? Because for the HTTP challenge I get following error:
`Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: jonode.duckdns.org
Type: dns
Detail: no valid A records found for jonode.duckdns.org; no valid AAAA records found for jonode.duckdns.org

Domain: jopanel.duckdns.org
Type: dns
Detail: no valid A records found for jopanel.duckdns.org; no valid AAAA records found for jopanel.duckdns.org

Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx server and that it is accessible from the internet.

Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
`

and for the dns challenge he wants me to deploy a TXT DNS record and I have no idea how to do that

[narrow cosmos]

There were too many logs to read @stoic wasp. Please post 5 or less. Alternatively, please share larger logs using paste sites, such as pteropaste or hastebin.

[lyric dagger]

Mine didn't work with a DNS either, I had to use the non SSL route

So I did everything with internal IP addresses, using the nginx without ssl to configure and when I create the node I use http

[median wind]

You need to own the domain or have a subdomain provided pointing to your server” panel “

[median wind]

That’s because your “ dns “ does not point to your “ server “

[stoic wasp]

Did you use the same IP for the node and then panel?

[stoic wasp]

So I can't use something like duckdns? How would I set up my own domain?

[stoic wasp]

COuld I use my duckdns but disable ssl?

[lyric dagger]

No I didn't, they were on separate machines. I don't know if you can use a ddns with SSL, but without the SSL I was able to use the ddns, like duck.

[stoic wasp]

I just bought a domain now and put up the DNS via there service so it should work when I come back home otherwise I may try your method. Thank you for your help

[lyric dagger]

Best of luck to you!

[stoic wasp]

Hey mate to witch of thous does the dns has to point to?
IPv4 address for docker0: 172.17.0.1
IPv4 address for ens33: 192.168.159.130
IPv4 address for pterodactyl0: 172.18.0.1
IPv6 address for pterodactyl0: fdba:17c8:6c94::1011

Currently my setup looks like this:

[stoic wasp]

I can use curl http://jonode.jobuddy.live and I get that outputhttps://pastebin.com/Taybr5HZ so I guess its pointing to the server

[median wind]

The public ip not internal

[stoic wasp]

yeah I figured that out like 2 seconds ago haha. That should be the right one I think 95.90.237.253

Requesting a certificate for jopanel.jobuddy.live

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: jopanel.jobuddy.live
Type: connection
Detail: 95.90.237.253: Fetching http://jopanel.jobuddy.live/.well-known/acme-challenge/66h3cDAiYww0Rc5Ax75ZIiOxV1cgmwMdKa5y4CbqaOc: Connection refused

Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx server and that it is accessible from the internet.

Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

I still get that error thougth

[median wind]

Are you installing panel on your personal pc?

[stoic wasp]

on an local server not my personal pc

[median wind]

Does this local server run trough a router ?

Did you port forward ? Checked firewall

[stoic wasp]

on 80 and nah I did not checked firewall what do I need to check?

[median wind]

You need to allow the ports on firewall to be able to communicate

[stoic wasp]

Where and how do I do that?

[median wind]

Google.com

Ask the bot for help