-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
[Pangolin] Badger calls pangolin:3001 #13436
Copy link
Copy link
Closed
Description
Script: Pangolin
Guidelines
- Read and understood guidelines: yes
- Verbose mode used: yes
Issue occurs during: Initial Creation / Installation
Environment
- Linux distribution: Debian
- Proxmox version: 9.1
- Default settings: Yes
- Advanced settings: No
- Exact command:
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/pangolin.sh)"
Description
I had another pangolin record in some DNS cache which was found by getent hosts pangolin, which is still called by badger. Doing echo "127.0.0.1 pangolin" >> /etc/hosts within the pangolin container fixed the issue.
This results in a 500 error with no sensible logs anywhere I could find.
Steps to reproduce
Install pangolin
Have a dns record/cache that resolves the hostname pangolin to something else
Badger calls pangolin:3001 and doesn't resolve correctly
Error output
N/A
Reporter has no GitHub username. Issue may be closed after 7 days without response.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels