mirror of
https://github.com/fosrl/pangolin.git
synced 2026-05-08 13:49:15 -05:00
[GH-ISSUE #772] Traefik is not starting after installing Pangolin. #10383
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/pangolin#10383
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @timsdeepsky on GitHub (May 23, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/772
Greetings,
I have tried to install Pangolin on a Racknerd vps with AlmaLinux 8 64 Bit multiple times, with no luck getting it to the dash board....
Following the install instructions and video link on the Fossorial Pangolin github site, the first few times i attempted to install Pangolin it failed to install any docker containers and would not go to the dashboard..The video link showed it installing the docker containers as part of the normal install process..I fixed this issue by installing docker before running the install process for Pangolin..(sudo dnf install docker-ce docker-ce-cli containerd.io docker-compose-plugin)..Finally was able to get Pangolin installed with the docker containers but hit another issue..
Container traefik does not start in pangolin..
Command i run in terminal to try to start docker containers:
(docker compose up -d)
The result in terminal:
✔ Container pangolin Healthy 1.0s
✔ Container gerbil Started 0.0s
⠋ Container traefik Starting 0.0s
Error response from daemon: Container 8fd503fb6f83d39d7bdd8483ca03378543b67eb4ffabc9f93164ca814b5f1b2f is restarting, wait until the container is running.
This traefik container never starts..I also have no access to the dashboard..
Question is:
How do i troubleshoot traefik not starting ??
I see nothing in the var/log/traefik.log
The "A" record and domain have been setup and pointed to the VPS ip address..
Ports 80-443-and 51820 are open in ufw:
224.0.0.251 5353/udp (mDNS) ALLOW IN Anywhere
80/tcp ALLOW IN Anywhere
443/tcp ALLOW IN Anywhere
51820/udp ALLOW IN Anywhere
80 ALLOW IN Anywhere
443 ALLOW IN Anywhere
51820 ALLOW IN Anywhere
22/tcp (SSH (v6)) ALLOW IN Anywhere (v6)
ff02::fb 5353/udp (mDNS) ALLOW IN Anywhere (v6)
80/tcp (v6) ALLOW IN Anywhere (v6)
443/tcp (v6) ALLOW IN Anywhere (v6)
51820/udp (v6) ALLOW IN Anywhere (v6)
80 (v6) ALLOW IN Anywhere (v6)
443 (v6) ALLOW IN Anywhere (v6)
51820 (v6) ALLOW IN Anywhere (v6)
80 ALLOW OUT Anywhere
443 ALLOW OUT Anywhere
51820 ALLOW OUT Anywhere
80 (v6) ALLOW OUT Anywhere (v6)
443 (v6) ALLOW OUT Anywhere (v6)
51820 (v6) ALLOW OUT Anywhere (v6)
Kernel version=4.18.0-513.5.1.el8_9.x86_64..
Traefik version=v3.3.6..
Docker version=26.1.3
1 GB KVM VPS Special Deal - Racknerd VPS
Extra IPv4: None
RAM: 1 GB RAM
CPU Cores: 1 CPU Core
Operating System: AlmaLinux OS 8
Thank you for any troubleshooting help you may have....
....UPDATE....5/24/2025....
As a test I installed Ubuntu 22.04 on the same Racknerd vps server instead of AlmaLinux 8 64 Bit....
I successfully installed Pangolin and was able to reach the dash board....
The sequence i used:
I updated the apt and packages,
Rebooted the Racknerd vps,
Installed ufw,
Opened ports 80 and 443 and 51820,
Installed Docker from this link=https://docs.docker.com/engine/install/ubuntu/
(using the latest version of Docker)
Installed Pangolin from the Github site,
It went right to the dash board with no problem....
Pure speculation, but appears that something in the wireguard area of AlmaLinux 8 64 Bit must be off....
I will continue to look and test....
Thank you....
@iwearoddsockz commented on GitHub (May 24, 2025):
I have the same issue with the exact same setup on Racknerd.
No output from 'docker logs traefik'
Do docker compose output:
[root@~]# docker compose up -d
[+] Running 3/4
✔ Network pangolin Created 0.2s
✔ Container pangolin Healthy 11.6s
✔ Container gerbil Started 11.1s
⠹ Container traefik Starting 11.7s
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to create new parent process: namespace path: lstat /proc/10176/ns/net: no such file or directory: unknown
Output from 'docker logs gerbil' shows that it seems to be an issue with WireGuard
gerbil | INFO: 2025/05/24 03:14:30 Fetching remote config from http://pangolin:3001/api/v1/gerbil/get-config
gerbil | FATAL: 2025/05/24 03:14:30 Failed to create WireGuard interface: operation not supported
@timsdeepsky commented on GitHub (May 24, 2025):
Greetings,
I agree....Numerous issues at terminal about Wireguard....
Am still investigating also....
Thank you....
@miloschwartz commented on GitHub (May 26, 2025):
Is WireGuard installed on your OS?
@timsdeepsky commented on GitHub (May 26, 2025):
Greetings Milo,
Wireguard was not found on the system and i could not get it to install either....
Thank you....
@timsdeepsky commented on GitHub (May 30, 2025):
Greetings,
I have not gained any more ground on a solution to this with the AlmaLinux 8 64 system on Racknerd vps....
Pangolin seems to work best for me with Ubuntu 20.04 operating system on Racknerd vps....
I will just use this....
Thank you....
@KielbasaMichal commented on GitHub (Jun 5, 2025):
Hi,
I also ran into a problem with the gerbil container - Failed to create WireGuard interface: operation not supported.
I found a similar issue reported in #471, and in my case, my VPS provider also doesn't support WireGuard kernel module.
One user proposed a new feature that would resolve issue #444, but unfortunately, such changes are not planned.
So currently there is probably no easy way to use Pangolin on such a system. I don't know if there is any possibility to configure Panglin to use different WireGuard tunnel (for example, created with wireguard-go).
Also, it will probably be worth to mention about that requirement in the docs Choosing a VPS
@github-actions[bot] commented on GitHub (Jun 20, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@oschwartz10612 commented on GitHub (Jun 22, 2025):
Yeah I think the recommendation now for
Failed to create WireGuard interface: operation not supportederrors on different VPS and OS platforms is to either install Wireguard to get the kernel module or use / upgrade to a kernel version that supports it. Right now we do not plan to change gerbil to not rely on the kernel module but could be done in the future.@silverjerk commented on GitHub (Jul 5, 2025):
Respectfully, I think you should strongly consider updating the installation docs and removing the recommendation for RackNerd's VPS. The VPS you link to, specifically, does not support the Wireguard module, and it cannot be installed manually -- kernal upgrades are also restricted at the provider level.
Ostensibly, what is likely the most appealing, cost effective solution that you point your users to, will not actually work using the basic installation instructions.
In my case, it fails at multiple stages; first during the Docker installation, and then after manually installing Docker, it hits a wall when installing Gerbil.
I understand this is an affiliate link and you guys should be paid for your hard work (Pangolin is great and I want to see it thrive), but depending on the affiliate share policy (typical affiliate programs pay out only after a user is subscribed for X number of days) you may be shorting yourself by simply not offering a pricier, but more competent service to your users. In my case, I'm cancelling and requesting a refund within 30 days of subscribing to their service.
@vtcosta commented on GitHub (Jul 6, 2025):
I've signed up for a RackNerd's VPS 3 days ago just to test pangolin, and I didn't have any issue.
Created my VPS with ubuntu 22.04, apt update & upgrade, did a few do-release-upgrade to the latest version (release 25.04, kernel 6.14.0-23-generic), installed docker as described in docker's documentation, and then installed pangolin with their installer, flawlessly. Maybe you should give it another try.
@silverjerk commented on GitHub (Jul 6, 2025):
You overlooked the context of both my comment, and this thread. As I pointed out in my reply, the instance Pangolin themselves are linking to (on the premise that it is the most economical option) runs AlmaLinux, and RackNerd's kernal version does not support the Wireguard module. Provider restrictions means you cannot update this yourself.
On Ubuntu, the installation works without issue. This is how I'm running Pangolin myself (on Hetzner).
Again, the OPs issue was signing up for the "cheap" RackNerd KVM and getting blocked during installation; this was my experience as well. I assume a lot of users coming to the docs are going to choose the cheapest option available, and the one conveniently linked to within the first few pages of the installation instructions.
Further, this restriction is not advertised by RackNerd, and RackNerd's TOS does not allow refunds for this service level. So if you're enticed by the bi-annual billing option for ~$20 for two years of service, you have effectively lost that $20 unless your diligent enough to push for a refund as, again, these restrictions aren't listed openly.
TLDR; the link Pangolin provides does not work for their default installation process. They're likely losing money because of this, and RackNerd's TOS means you might too -- myself and OP ran into the exact same issue. My comment isn't about not being able to run Pangolin, so much as advising that affiliate link be removed to prevent frustration for other end-users who may not have the chops to diagnose the issue, understand the restriction, and seek out another provider/service level.
@vtcosta commented on GitHub (Jul 6, 2025):
The affiliate link is not limited to AlmaLinux, you can choose a bunch of different OSes, as can be seen in the image below:
Even if you initially chose AlmaLinux, you can install a different OS afterwards through their control panel (reinstall button).
Maybe there is some sort of incompatibility with AlmaLinux, and that should mentioned in pangolins referral page.
Again, I've signed up for a VPS with RackNerd through their affiliate link, and didn't have any issue whatsoever with their Ubuntu 22.04.
I recommend upgrading the system to the latest version before doing anything with it. As I said, I managed to update Ubuntu to version 25.04, kernel 6.14.0-23-generic.
@oschwartz10612 commented on GitHub (Jul 6, 2025):
^^^ Yeah you can choose any os and I dont think our link can pick one but I will reach out to RackNerd and see if we can!
We do have some issues on Alma - not super familiar with the disro myself but it does not seem to play nice. Fadora, ubuntu, and debian users typically have good luck with!