April 5, 20251 yr Author 5 minutes ago, Uplinkpro said: That fixed it, now im having issues starting wings says no file is there but it absolutely is and its able to access it this is the log : INFO: [Apr 5 09:33:59.805] writing log files to disk path=/var/log/pelican/wings.log INFO: [Apr 5 09:33:59.805] loading configuration from file config_file=/etc/pelican/config.yml INFO: [Apr 5 09:33:59.809] configured wings with system timezone timezone=America/Los_Angeles INFO: [Apr 5 09:33:59.809] configured system user successfully gid=100 uid=99 username=nobody INFO: [Apr 5 09:33:59.810] fetching list of servers from API INFO: [Apr 5 09:34:00.058] processing servers returned by the API total_configs=0 INFO: [Apr 5 09:34:00.058] finished processing server configurations duration=57.358µs INFO: [Apr 5 09:34:00.060] configuring system crons interval=1m0s subsystem=cron INFO: [Apr 5 09:34:00.060] starting cron processes subsystem=cron INFO: [Apr 5 09:34:00.060] updating server states on Panel: marking installing/restoring servers as normal INFO: [Apr 5 09:34:00.060] configuring internal webserver host_address=0.0.0.0 host_port=8443 use_auto_tls=false use_ssl=true FATAL: [Apr 5 09:34:00.060] failed to configure HTTPS server auto_tls=false error=open /etc/letsencrypt/live/node.upclutch.xyz/fullchain.pem: no such file or directory Stacktrace: open /etc/letsencrypt/live/node.upclutch.xyz/fullchain.pem: no such file or directory github.com/pelican-dev/wings/cmd.rootCmdRun github.com/pelican-dev/wings/cmd/root.go:392 github.com/spf13/cobra.(*Command).execute github.com/spf13/[email protected]/command.go:989 github.com/spf13/cobra.(*Command).ExecuteC github.com/spf13/[email protected]/command.go:1117 github.com/spf13/cobra.(*Command).Execute github.com/spf13/[email protected]/command.go:1041 github.com/pelican-dev/wings/cmd.Execute github.com/pelican-dev/wings/cmd/root.go:71 main.main ./wings.go:17 runtime.main runtime/proc.go:271 runtime.goexit runtime/asm_amd64.s:1695 My config.yml : debug: false uuid: ef7170ba-047f-4e9c-8360-d0f8b125af29 token_id: slX4KidQjXLT8bH1 token: JABT7ebQA8NPFMBcPwHWcaGAk22wJfNwMignEBWxrh1r49XJG6myEIgpo7OJvMF5 api: host: 0.0.0.0 port: 8443 ssl: enabled: true cert: /etc/letsencrypt/live/node.upclutch.xyz/fullchain.pem key: /etc/letsencrypt/live/node.upclutch.xyz/privkey.pem upload_limit: 1024 system: data: /mnt/user/appdata/pelican-wing/data sftp: bind_port: 2022 allowed_mounts: [] remote: 'https://panel.upclutch.xyz' Finally my docker config for wings is below, if i use ssl it will not fully boot wings, If I attempt just port 8080 it will boot but panel will never see it. If you use the wing behind a reverse proxy, you need to disable the SSL ssl: enabled: false otherwise it needs the certificate also, your port in the config is wrong. it should be 8080. Otherwise create a port mapping for 8443 Edited April 5, 20251 yr by Mainfrezzer
April 5, 20251 yr 8 minutes ago, Mainfrezzer said: If you use the wing behind a reverse proxy, you need to disable the SSL ssl: enabled: false otherwise it needs the certificate also, your port in the config is wrong. it should be 8080. Otherwise create a port mapping for 8443 Updated config, this one fully boots wings however panel will not see it: debug: false uuid: ef7170ba-047f-4e9c-8360-d0f8b125af29 token_id: slX4KidQjXLT8bH1 token: JABT7ebQA8NPFMBcPwHWcaGAk22wJfNwMignEBWxrh1r49XJG6myEIgpo7OJvMF5 api: host: 0.0.0.0 port: 8080 ssl: enabled: false cert: /etc/letsencrypt/live/node.upclutch.xyz/fullchain.pem key: /etc/letsencrypt/live/node.upclutch.xyz/privkey.pem upload_limit: 1024 system: data: /mnt/user/appdata/pelican-wing/data sftp: bind_port: 2022 allowed_mounts: [] remote: 'https://panel.upclutch.xyz' The heart stays red and if you go to the node it says this: {"error":"The required authorization heads were not present in the request."}
April 5, 20251 yr Author 1 minute ago, Uplinkpro said: Updated config, this one fully boots wings however panel will not see it: debug: false uuid: ef7170ba-047f-4e9c-8360-d0f8b125af29 token_id: slX4KidQjXLT8bH1 token: JABT7ebQA8NPFMBcPwHWcaGAk22wJfNwMignEBWxrh1r49XJG6myEIgpo7OJvMF5 api: host: 0.0.0.0 port: 8080 ssl: enabled: false cert: /etc/letsencrypt/live/node.upclutch.xyz/fullchain.pem key: /etc/letsencrypt/live/node.upclutch.xyz/privkey.pem upload_limit: 1024 system: data: /mnt/user/appdata/pelican-wing/data sftp: bind_port: 2022 allowed_mounts: [] remote: 'https://panel.upclutch.xyz' The heart stays red and if you go to the node it says this: {"error":"The required authorization heads were not present in the request."} you need to turn ssl in the panel on. the panel is trying to reach your node over http
April 5, 20251 yr 3 minutes ago, Mainfrezzer said: you need to turn ssl in the panel on. the panel is trying to reach your node over http Tried that still same issue:
April 5, 20251 yr Author Just now, Uplinkpro said: Tried that still same issue: what port did you enter in the panel for the node address? i hope its 443 and not 8443^^
April 5, 20251 yr 1 minute ago, Mainfrezzer said: what port did you enter in the panel for the node address? i hope its 443 and not 8443^^ Facepalming myself it was 8080 still popped in 443 and we are green. I think thie text under the panel confused me "If you are running the daemon behind Cloudflare you should set the daemon port to 8443 to allow websocket proxying over SSL."
April 5, 20251 yr Author 1 minute ago, Uplinkpro said: Facepalming myself it was 8080 still popped in 443 and we are green. I think thie text under the panel confused me "If you are running the daemon behind Cloudflare you should set the daemon port to 8443 to allow websocket proxying over SSL." yeah what the cloudflare notice is about, i personally have no clue either. Never seen it not work over the default 443. Even cloudflare states Quote Cloudflare supports proxied WebSocket connections without additional configuration.
April 6, 20251 yr Hello again! I have problem with websocket connection. Can you pls help me. my node settings
April 6, 20251 yr Author 9 minutes ago, albatraus said: Hello again! I have problem with websocket connection. Can you pls help me. my node settings I assume it worked until you updated the panel container with the update that i pushed yesterday? Setting the owner of your pelican-panel folder in appdata to nobody might fix it. I had to change user and group ids. Otherwise i assume the wing itself works fine when you visit the address?
April 6, 20251 yr Hi sorry to bother you guys but does anyone know why my text editor is just scrunched up like this? I've already searched here and found a fix with uploading files, which I really appreciate so much to the person that posted that about adding the IP address to the list! But now i'm just stuck with the editor looking like this, I've tried using different browsers, Edge, Vivalidi, A few chromium based browsers and firefox based ones as well and they all show up like that. I even tried my phone and it looks like that .-.
April 6, 20251 yr 3 hours ago, Mainfrezzer said: I assume it worked until you updated the panel container with the update that i pushed yesterday? Setting the owner of your pelican-panel folder in appdata to nobody might fix it. I had to change user and group ids. Otherwise i assume the wing itself works fine when you visit the address? I had to delete it because servers suddenly stopped working. And now I reinstalled it. Changing owner didn't helped:( Wing works well when i visit the address.
April 6, 20251 yr Author 2 minutes ago, tier1kill said: Hi sorry to bother you guys but does anyone know why my text editor is just scrunched up like this? I've already searched here and found a fix with uploading files, which I really appreciate so much to the person that posted that about adding the IP address to the list! But now i'm just stuck with the editor looking like this, I've tried using different browsers, Edge, Vivalidi, A few chromium based browsers and firefox based ones as well and they all show up like that. I even tried my phone and it looks like that .-. For some reason its not loading/failing to load a css file. ive had that happen to me once too. and it just happened again to me too ill look into it too see whats causing it.
April 6, 20251 yr 8 minutes ago, Mainfrezzer said: For some reason its not loading/failing to load a css file. ive had that happen to me once too. and it just happened again to me too ill look into it too see whats causing it. Sounds good thanks!
April 6, 20251 yr Has anyone else's updated and after no longer able to connect to their node. I have changed the Pelican owner to 'nobody' as suggested above but no node connection. Assume something in a update has changed as it worked great previously with multiple servers "Failed to load resource: the server responded with a status of 404 (Not Found)"
April 6, 20251 yr Author 1 hour ago, tier1kill said: Sounds good thanks! its an odd bug, it a 50:50 if it appears or not while building the image, ill pushed an update Edited April 6, 20251 yr by Mainfrezzer
April 6, 20251 yr 9 minutes ago, Mainfrezzer said: its an odd bug, it a 50:50 if it appears or not while building the image, ill pushed an update Fantastic! thanks!
April 6, 20251 yr IT WORKS! Thank you so much! I can finally edit everything in the panel without having studio code open on a different monitor 😅
April 6, 20251 yr Author 1 hour ago, Mainfrezzer said: For some reason its not loading/failing to load a css file. ive had that happen to me once too. and it just happened again to me too ill look into it too see whats causing it. 1 hour ago, DaFr0n said: Has anyone else's updated and after no longer able to connect to their node. I have changed the Pelican owner to 'nobody' as suggested above but no node connection. Assume something in a update has changed as it worked great previously with multiple servers "Failed to load resource: the server responded with a status of 404 (Not Found)" there are logs in "/mnt/cache/appdata/pelican-panel/pelican-log" assuming its the default path, would be good to know the errors laravel is throwing
April 6, 20251 yr Author 16 minutes ago, DaFr0n said: laravel-2025-04-06.log Logs attached just out of curiosity, if you update the container to the one i pushed a bit ago, is it still broken?
April 6, 20251 yr 1 hour ago, Mainfrezzer said: just out of curiosity, if you update the container to the one i pushed a bit ago, is it still broken? Yes updated wings and panel, still the same issue.
April 7, 20251 yr Author 10 hours ago, DaFr0n said: Yes updated wings and panel, still the same issue. odd, you can use the "old"-pre-id change panel with "ghcr.io/mainfrezzer/pelican-panel@sha256:e215e2d2a7a8efe502cce052ade1cd781df67ad732749a6118dcdd92d0a552f7" that one apparently also has the missing css tho. If that works ive to do some diging.
April 7, 20251 yr 10 hours ago, Mainfrezzer said: odd, you can use the "old"-pre-id change panel with "ghcr.io/mainfrezzer/pelican-panel@sha256:e215e2d2a7a8efe502cce052ade1cd781df67ad732749a6118dcdd92d0a552f7" that one apparently also has the missing css tho. If that works ive to do some diging. Just tried the above, same issue mate
April 7, 20251 yr Author 5 minutes ago, DaFr0n said: Just tried the above, same issue mate well thats at least good news for me, means i didnt break it with the id change. You could test it with the official docker container from the pelican devs to see if works there but i have a high suspicion that the issue occures there too since i didnt touch anything apart from some paths
April 7, 20251 yr 23 minutes ago, Mainfrezzer said: well thats at least good news for me, means i didnt break it with the id change. You could test it with the official docker container from the pelican devs to see if works there but i have a high suspicion that the issue occures there too since i didnt touch anything apart from some paths Problem solved... I'm not sure how this happened but my Pelican-Wings changed to pulling ghcr.io/mainfrezzer/pelican-panel:latest I have changed this back to wings:latest & all is well. Thanks for the help
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.