Ptero Errors
Having some issues getting the panel back going after a sudo reboot
19 Replies
Fetch the last few lines of your MariaDB logs from somewhere in /var/log
Might be under mariadb or mysql
To be clear, did you get Redis to start successfully?
nope
and nothing in the mysql logs
That is redis log
twas a permission issue
They both look like permission issues
yep
its working fine
w chatgpt
ChatGPT is very useful if you can check if what you did worked afterwards, but just in case I'd recommend always including at the end of your prompt
"Also, give me the steps I would need to take to un-do this if it doesn't work or has unintended consequences. If I need to give you more information for you to know how to undo it, let me know what information you need."
okay great cause my next plan is to somehow move the panel to my AWS instance and connect it back to this server it's currently on
but i dont want to lose servers that are spun up
Panel and Wings are completely separate. You can migrate the panel without worrying about losing servers; you'll just need to connect it to Wings again.
yeah i gotta figure out how to move the panel and blueprint and all that and then connect it back.
Im trying to do this in production soooo danger
Just don't remove anything from your current server until AFTER everything's working on the new one.
do i just go into nodes and map it to the domain?
This look right?
No, that looks like AI hallucinations. Use the migrate guide for the panel.
https://gist.github.com/trenutoo/c18258658bef28e73b24d11d02d24915#migrating-panel
You'll have to update your Database Host user's host and your Wings machine's firewall afterwards as well.
Wings machine:
Panel:
- Change host in database host to your Wings machine's public IP instead of 127.0.0.1
Okay so far I got the node setup and green heartbeat. Im working on allocations now. After I finish that I should run those commands above correct?
to clarify I have the node on the main server connected to the panel on the aws
Yes, but obviously replacing new_panel_ip with the actual IP of your AWS panel.
got it
i'll give it a shot. i messed up and put the public ip in the ip portion so now i have to delete 89 pages of allocations
a command for this would be goals
What potentially can cause this?
oh i see. so i have to set the ip of the node machine or the panel machine?
boom. fixed