#Red Heart in Panel

1 messages · Page 1 of 1 (latest)

calm locustBOT
#

We need some logs from you in order to help debug this issue.
Panel: tail -n 150 /var/www/pterodactyl/storage/logs/laravel-$(date +%F).log | nc pteropaste.com 99
Wings: sudo wings diagnostics
Please see .plogs and .wlogs respectively for more information.

#

I have found the following for: https://ptero.co/terasimoxi
@lost herald; You don't appear to be providing a password for your database connection. Make sure to provide one in your .env file or all authentication attempts will fail. Open the file and find DB_PASSWORD variable, do not add a new one. Remember to enclose it in double quotes such as DB_PASSWORD="mypassword"

You can open it directly with nano /var/www/pterodactyl/.env. Refresh config cache with cd /var/www/pterodactyl && php artisan config:clear

I have found the following for: https://ptero.co/udehugofic
At your service, @lost herald!

The IP address you have assigned to your server is not actually available for use on your machine, or something is already running on that port. Use ss -plnt | grep :<port> (replacing <port> with your own) to find what processes might be using it.

If you don't find any service using the port, then refer to the instructions below.

Execute the command hostname -I | awk '{print $1}' and change your Node allocations to use this IP. Yes, it can be your internal/local IP when you're behind NAT. You still have to use it as that is your network interface IP.

If you have added multiple public IPs to your network interface, then you can view all of them using the command ip a | grep "inet "

lost herald
#

Database password was already set in config
and only thing on port 8080 is wings

green tangle
#

its looking at older logs.

#

port 8080 isnt open. So the panel cant reach wings

#

check your firewal settings

lost herald
#

DEBUG: [Jun 4 22:45:47.978] GET /api/system client_ip=188.245.170.156 latency=39.493834ms request_id=cf3f4067-84ff-49f7-984d-f4c0f17c2325 status=200

#

firewall is open

#

get requests are 200 OK

green tangle
#

still timed-out

lost herald
#

firewall is only open to panel

#

why should i open it for everyone?

green tangle
#

how else are people going to connect to your servers? They have to connect to your node

lost herald
#

but on different ports which are open for everyone

green tangle
#

panel isnt able to communicate to your wings. It has nothing to do with ptero and is purely networking related

#

maybe its a nat loopback issue although i doubt it

calm locustBOT
#

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
lost herald
#

why do they have to be open to everyone? i configured an open firewall to panel and node and backwards