Bug Reports

Environment Variables for my Chatwoot Application are not loading Hello, I am experiencing a critical issue with my Chatwoot deployment. I have configured all the necessary SMTP environment variables through the EasyPanel UI, but the application is unable to send emails. I have verified that the problem is not with the configuration itself, but with EasyPanel failing to pass the variables to the container. Key Evidence of the Problem: The Container Cannot See the Variables: I executed th command env and confirmed that the SMTP_ADDRESS, SMTP_PORT, etc., variables are not present in the container's environment. The Application is Using the Default Configuration: The logs from my chatwoot-sidekiq container show the following error, which indicates that Chatwoot is not seeing my SMTP configuration and is attempting to use a local (sendmail) configuration. -------- sendmail: can't connect to remote host (127.0.0.1): Connection refused -------- Related Deployment Issue: I have also noticed that my service deployments are failing due to a syntax error in a Supabase configuration file that I no longer use. This could be related to the variable injection problem. Could you guys please help me diagnose and resolve why EasyPanel is not loading the environment variables into my containers? Thank you.

Environment Variables for my Chatwoot Application are not loading Hello, I am experiencing a critical issue with my Chatwoot deployment. I have configured all the necessary SMTP environment variables through the EasyPanel UI, but the application is unable to send emails. I have verified that the problem is not with the configuration itself, but with EasyPanel failing to pass the variables to the container. Key Evidence of the Problem: The Container Cannot See the Variables: I executed th command env and confirmed that the SMTP_ADDRESS, SMTP_PORT, etc., variables are not present in the container's environment. The Application is Using the Default Configuration: The logs from my chatwoot-sidekiq container show the following error, which indicates that Chatwoot is not seeing my SMTP configuration and is attempting to use a local (sendmail) configuration. -------- sendmail: can't connect to remote host (127.0.0.1): Connection refused -------- Related Deployment Issue: I have also noticed that my service deployments are failing due to a syntax error in a Supabase configuration file that I no longer use. This could be related to the variable injection problem. Could you guys please help me diagnose and resolve why EasyPanel is not loading the environment variables into my containers? Thank you.

trying to change the supabase .env, and this just make supabase not working! looks like is related to this bug https://github.com/easypanel-io/compose/issues/10

The Supabase template isn't working correctly, especially the realtime function. It would be really helpful if we could have an update that includes all the functionalities of this tool. If it's possible to resolve this issue, it would be greatly appreciated. Thank you in advance!

Installed AdguardHome from templates, but it stuck on Yellow state

Hi! My n8n instance suddenly started showing this error without any changes from my side: Origin header does NOT match the expected origin. (Origin: " https://n8n.gestaoias.shop ", Expected: "wss: //n8n.gestaoias.shop ") It looks like WebSocket is not being routed correctly by the reverse proxy. The n8n editor depends on WebSocket to work properly. Everything was working fine before. Could this be a proxy or SSL issue? Can you help me check if WebSocket forwarding is enabled or if something changed in the proxy settings? Thank you in advance!

Fresh Installed VPS and Jellyfin with Easypanel. In quick start, after input admin name and password, click submit, then nothing changes

After updating my EasyPanel to V16, Traefik's RAM consumption increased considerably, to the point of consuming all of the server's available RAM. And we didn't have this problem in version 15. Can you help me with this?

When open in browser: Blocked request. This host (" bolt.bla.bla.easypanel.host ") is not allowed. To allow this host, add " bolt.bla.bla.easypanel.host " to server.allowedHosts in vite.config.js.