January 10, 20251 yr How can I run this in bridge mode? 8834387b94b9323278b34119aa850666e2dc4a483f54bac6ac886ccf7716aa7a docker: Error response from daemon: driver failed programming external connectivity on endpoint AdGuard-Home-Unbound (5384ba01eda962128f8b6d4653fd5feeccd5e72636b884b305f52dbabd172e01): failed to bind port 0.0.0.0:53/tcp: Error starting userland proxy: listen tcp4 0.0.0.0:53: bind: address already in use. The command failed. Edited January 10, 20251 yr by kri kri
January 10, 20251 yr Author 45 minutes ago, kri kri said: How can I run this in bridge mode? 8834387b94b9323278b34119aa850666e2dc4a483f54bac6ac886ccf7716aa7a docker: Error response from daemon: driver failed programming external connectivity on endpoint AdGuard-Home-Unbound (5384ba01eda962128f8b6d4653fd5feeccd5e72636b884b305f52dbabd172e01): failed to bind port 0.0.0.0:53/tcp: Error starting userland proxy: listen tcp4 0.0.0.0:53: bind: address already in use. The command failed. If you really want to run this in bridge mode, you have to disable the VM Service Edit: I mean, unless you actually dont use regular dns requests, which i highly doubt. But if thats the case, just change the port 53. But otherwise, 53 is the default for all regular dns requests and the VM Manager occupies that port already. Edited January 10, 20251 yr by Mainfrezzer
January 10, 20251 yr Author 5 minutes ago, kri kri said: How would you run it? on br0/eth0 with its own ip
January 11, 20251 yr Hello. I have a problem. The wing and panel are not communicating, but the wing and panel are working. Here is a wing log: INFO: [Jan 11 13:47:04.316] writing log files to disk path=/var/log/pelican/wings.log INFO: [Jan 11 13:47:04.317] loading configuration from file config_file=/etc/pelican/config.yml INFO: [Jan 11 13:47:04.322] configured wings with system timezone timezone=Europe/Athens INFO: [Jan 11 13:47:04.322] configured system user successfully gid=100 uid=99 username=nobody INFO: [Jan 11 13:47:04.323] fetching list of servers from API INFO: [Jan 11 13:47:04.442] processing servers returned by the API total_configs=0 INFO: [Jan 11 13:47:04.442] finished processing server configurations duration=57.574µs INFO: [Jan 11 13:47:04.443] configuring system crons interval=1m0s subsystem=cron INFO: [Jan 11 13:47:04.443] starting cron processes subsystem=cron INFO: [Jan 11 13:47:04.443] updating server states on Panel: marking installing/restoring servers as normal INFO: [Jan 11 13:47:04.443] configuring internal webserver host_address=0.0.0.0 host_port=8002 use_auto_tls=false use_ssl=false INFO: [Jan 11 13:47:04.444] sftp server listening for connections listen=0.0.0.0:2022 public_key=XXXXXX INFO: [Jan 11 14:02:45.081] writing log files to disk path=/var/log/pelican/wings.log INFO: [Jan 11 14:02:45.081] loading configuration from file config_file=/etc/pelican/config.yml INFO: [Jan 11 14:02:45.086] configured wings with system timezone timezone=Europe/Athens INFO: [Jan 11 14:02:45.087] configured system user successfully gid=100 uid=99 username=nobody INFO: [Jan 11 14:02:45.088] fetching list of servers from API INFO: [Jan 11 14:02:47.597] processing servers returned by the API total_configs=0 INFO: [Jan 11 14:02:47.598] finished processing server configurations duration=65.81µs INFO: [Jan 11 14:02:47.599] configuring system crons interval=1m0s subsystem=cron INFO: [Jan 11 14:02:47.599] starting cron processes subsystem=cron INFO: [Jan 11 14:02:47.599] updating server states on Panel: marking installing/restoring servers as normal INFO: [Jan 11 14:02:47.600] configuring internal webserver host_address=0.0.0.0 host_port=8002 use_auto_tls=false use_ssl=false INFO: [Jan 11 14:02:47.601] sftp server listening for connections listen=0.0.0.0:2022 public_key=XXXXXX Here is my wing setup Config: I have no idea why it's not working Edited January 11, 20251 yr by albatraus
January 11, 20251 yr Author 1 hour ago, albatraus said: Hello. I have a problem. The wing and panel are not communicating, but the wing and panel are working. Here is a wing log: INFO: [Jan 11 13:47:04.316] writing log files to disk path=/var/log/pelican/wings.log INFO: [Jan 11 13:47:04.317] loading configuration from file config_file=/etc/pelican/config.yml INFO: [Jan 11 13:47:04.322] configured wings with system timezone timezone=Europe/Athens INFO: [Jan 11 13:47:04.322] configured system user successfully gid=100 uid=99 username=nobody INFO: [Jan 11 13:47:04.323] fetching list of servers from API INFO: [Jan 11 13:47:04.442] processing servers returned by the API total_configs=0 INFO: [Jan 11 13:47:04.442] finished processing server configurations duration=57.574µs INFO: [Jan 11 13:47:04.443] configuring system crons interval=1m0s subsystem=cron INFO: [Jan 11 13:47:04.443] starting cron processes subsystem=cron INFO: [Jan 11 13:47:04.443] updating server states on Panel: marking installing/restoring servers as normal INFO: [Jan 11 13:47:04.443] configuring internal webserver host_address=0.0.0.0 host_port=8002 use_auto_tls=false use_ssl=false INFO: [Jan 11 13:47:04.444] sftp server listening for connections listen=0.0.0.0:2022 public_key=XXXXXX INFO: [Jan 11 14:02:45.081] writing log files to disk path=/var/log/pelican/wings.log INFO: [Jan 11 14:02:45.081] loading configuration from file config_file=/etc/pelican/config.yml INFO: [Jan 11 14:02:45.086] configured wings with system timezone timezone=Europe/Athens INFO: [Jan 11 14:02:45.087] configured system user successfully gid=100 uid=99 username=nobody INFO: [Jan 11 14:02:45.088] fetching list of servers from API INFO: [Jan 11 14:02:47.597] processing servers returned by the API total_configs=0 INFO: [Jan 11 14:02:47.598] finished processing server configurations duration=65.81µs INFO: [Jan 11 14:02:47.599] configuring system crons interval=1m0s subsystem=cron INFO: [Jan 11 14:02:47.599] starting cron processes subsystem=cron INFO: [Jan 11 14:02:47.599] updating server states on Panel: marking installing/restoring servers as normal INFO: [Jan 11 14:02:47.600] configuring internal webserver host_address=0.0.0.0 host_port=8002 use_auto_tls=false use_ssl=false INFO: [Jan 11 14:02:47.601] sftp server listening for connections listen=0.0.0.0:2022 public_key=XXXXXX Here is my wing setup Config: I have no idea why it's not working Does the website for the Wing panel display anything when you visit it? i.e. if you do not see that message, then your forwarding/proxying is off. Since i dont know how you have your reverse proxy setup, i can only guess that youre maybe missing the correct port export in the template. The default thats set is 8080, so in your case, you would have to add a new port mapping on 8002 in the container.
January 11, 20251 yr I just needed to change the container port to get it to work. I guess i had same issue with pterodactyl set up. Because before this i tried to get it work. Thank you so much!
February 10, 20251 yr Mysql-client is not installed on the container, if you can update the docker so it will stop mysql erros.
February 14, 20251 yr @Mainfrezzer should the beta `pelican-panel:latest` image be working? i have a fresh install and i cant access /installer. `502 Bad Gateway`. I can run the installer using the tag `pelican-dev/panel:latest`
February 14, 20251 yr Author 4 minutes ago, KeyBoardDabbler said: @Mainfrezzer should the beta `pelican-panel:latest` image be working? i have a fresh install and i cant access /installer. `502 Bad Gateway`. I can run the installer using the tag `pelican-dev/panel:latest` How do you access that? Did you keep the reverse proxy mapping?
February 14, 20251 yr 42 minutes ago, Mainfrezzer said: How do you access that? Did you keep the reverse proxy mapping? on the original image i removed the proxy mapping, this worked with no issue. I have also had it running behind SWAG. The new image I've tried many different combinations but cant access the webUI.
February 14, 20251 yr Author 2 hours ago, KeyBoardDabbler said: on the original image i removed the proxy mapping, this worked with no issue. I have also had it running behind SWAG. The new image I've tried many different combinations but cant access the webUI. Mind sharing how you set it up? Template settings of pelican and how you setup your reverse proxy to access it. ive tried here a couple things and i cant replicate it, apart from the wonky too many redirect thing.
February 14, 20251 yr 9 hours ago, Mainfrezzer said: Mind sharing how you set it up? Template settings of pelican and how you setup your reverse proxy to access it. ive tried here a couple things and i cant replicate it, apart from the wonky too many redirect thing. I tried accessing the local IP without being behind the reverse proxy, for this i removed the Proxy Workaround. However this failed to load. I then replicated my working setup on the original image but this failed to load as well. Original image I have a Cloudflare Tunnel pointing to the SWAG container, this forwards traffic to the IP:Port of the panel container and is accessible at the APP_URL. Beta image seems to not get passed the NGINX step.
February 14, 20251 yr Very strange, I have not changed anything since my post and I can now access local and APP URL on beta image. Restarted the container and it hangs at the NGINX step again, unable to access web panel. Edited February 14, 20251 yr by KeyBoardDabbler
February 14, 20251 yr Author 9 minutes ago, KeyBoardDabbler said: I tried accessing the local IP without being behind the reverse proxy, for this i removed the Proxy Workaround. However this failed to load. I then replicated my working setup on the original image but this failed to load as well. Original image I have a Cloudflare Tunnel pointing to the SWAG container, this forwards traffic to the IP:Port of the panel container and is accessible at the APP_URL. Beta image seems to not get passed the NGINX step. The "beta" image, is the image i build^^ Both are beta. My container, i.e. mainfrezzer-pelican-panel, you have to wait a tat longer. It runs chown at startup as a fix for permissions in it that prevents the error 500 that pops up. Its done with that when supervisord pops up. (can depend on disk speed) The issue with the official image ill have to check out. I wouldnt be surprised if this is an issue specifially with caddy (not the first issue caddy has, thats why i use nginx)
February 14, 20251 yr 23 minutes ago, Mainfrezzer said: The "beta" image, is the image i build^^ Both are beta. My container, i.e. mainfrezzer-pelican-panel, you have to wait a tat longer. It runs chown at startup as a fix for permissions in it that prevents the error 500 that pops up. Its done with that when supervisord pops up. (can depend on disk speed) The issue with the official image ill have to check out. I wouldnt be surprised if this is an issue specifially with caddy (not the first issue caddy has, thats why i use nginx) That makes sense now, i appreciate your input. Can confirm the error 500 has not popped up yet either.. Regarding the wings image, do i need to change the port from 8080 to 8433 if going through Cloudflare. DNS check is valid but health check is unable to connect. Edited February 14, 20251 yr by KeyBoardDabbler
February 14, 20251 yr Author 3 minutes ago, KeyBoardDabbler said: That makes sense now, i appreciate your input. Can confirm the error 500 has not popped up yet either.. Regarding the wings image, do i need to change the port from 8080 to 8433 if going through Cloudflare. DNS check is valid but health check is unable to connect. For the config.yml itself, you have to change it to whatever is running inside the container and is mapped to the outside. I.e. by default the config yaml inside the wings appdata folder should have 8080 the cloudflare thing is only a webgui thing, i didnt test the wing with cloudflare, so its either 443 or 8443
February 14, 20251 yr 7 minutes ago, Mainfrezzer said: the cloudflare thing is only a webgui thing, i didnt test the wing with cloudflare, so its either 443 or 8443 while making sure i stopped the container and updated the config.yml, i have tried 8080, 433 and 8443 with no luck. I also changed this on the template and nginx to match.
February 14, 20251 yr Author 3 minutes ago, KeyBoardDabbler said: while making sure i stopped the container and updated the config.yml, i have tried 8080, 433 and 8443 with no luck. I also changed this on the template and nginx to match. I would recommend putting SSL: to false in the config should have complained about missing certs in the log
February 14, 20251 yr 3 minutes ago, Mainfrezzer said: I would recommend putting SSL: to false in the config should have complained about missing certs in the log I included the certs in the correct path to prevent the fatal error. Unfortunately this does not help and still unable to get a healthy status.
February 14, 20251 yr Author 29 minutes ago, KeyBoardDabbler said: I included the certs in the correct path to prevent the fatal error. Unfortunately this does not help and still unable to get a healthy status. What a convoluted way to provide certs and then also reverse proxy. That said, i honestly have no clue if native https works on the wings, never tested it. also, i can conclude. its working fine with cloudflare tunnels on 443 wing template Webpanel settings Result Im gonna resume trying to re-create your error 502 double reverse proxy issue now^^ @KeyBoardDabbler im pretty sure the 502 is a swag issue. ive encountered this issue once before with nginx the proxy_pass uses variables and malforms the request. When change the proxy_pass to the proper written out "http://10.0.80.20:80" then it worked. Edit: The odd thing was, i even only used swag to go one hop. All i tried to access with it was 192.168.2.2:800 and gave me a 502, while being able to curl it. then i tried my unraid server it failed too. After changing it back to variables, it seems to work again. But no clue why, maybe cache. who knows Edit: heres the malform issue mentioned https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4102 Edited February 14, 20251 yr by Mainfrezzer added missing config.yml picture
February 14, 20251 yr 15 minutes ago, Mainfrezzer said: also, i can conclude. its working fine with cloudflare tunnels on 443 I have the same settings, although the Cloudflare tunnel points to swag and it doesn't communicate. I will try connecting the tunnel straight to the wings container.
February 14, 20251 yr Author 7 minutes ago, KeyBoardDabbler said: I have the same settings, although the Cloudflare tunnel points to swag and it doesn't communicate. I will try connecting the tunnel straight to the wings container. That reminds me, in nginx, you need to set something if you want to access ssl pages through the proxy proxy_ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3; proxy_ssl_server_name on; one of those 2 it was im pretty sure, cloudflare has something similar for the proxied pages, but no clue on tunnels Edit: to check if the wing is properly working curl -L ADDRESSOFWING curl should say: {"error":"The required authorization heads were not present in the request."} when its working Edited February 14, 20251 yr by Mainfrezzer
February 14, 20251 yr 14 minutes ago, Mainfrezzer said: That reminds me, in nginx, you need to set something if you want to access ssl pages through the proxy proxy_ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3; proxy_ssl_server_name on; one of those 2 it was im pretty sure, cloudflare has something similar for the proxies pages, but no clue on tunnels I found ssl_protocols but not proxy_ssl_protocols. I also tried connecting the tunnel direct to the container instead of going through swag with no luck. You mentioned "its working fine with cloudflare tunnels on 443" but your template is using 8080?
February 14, 20251 yr Author 12 minutes ago, KeyBoardDabbler said: I found ssl_protocols but not proxy_ssl_protocols. I also tried connecting the tunnel direct to the container instead of going through swag with no luck. You mentioned "its working fine with cloudflare tunnels on 443" but your template is using 8080? The container itself uses 8080. Because 8080 is forwarded to unraid. The cloudflare tunnel is directed to redirect wing.magnon.ovh to 172.17.0.1:8080 Anyone who wants to access https://wing.magnon.ovh is automatically directed to port 443, because its the default port. Its detached. Everything that is in the container, stays in the container. No matter what you change the template to, if its 3888, 47578 or 30000. As long as the template say, it stays Port 8080. What the cloudflare tunnel(or any proxy) is pointing to, is whatever you set here And the webgui will use the default 443(since it worked) Edit: If you dont use Unraid as the target, ie either lan ip or the internal docker host 172.17.0.1 its whatever the container port is period. if the container is running on the bridge with 172.17.0.20. its 172.17.0.20:8080 unless you did change the port in the config.yml, then its 172.17.0.20:Whatevertheconfig.yml says Edited February 14, 20251 yr by Mainfrezzer
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.