Bug Reports

not working in digitalocean and linode

After I recently updated to latest version I can not run yarn commands. all commands timeout saying fetching.... when I launch the apps using dockerfile command. I tried npm and pnpm commands too both too also stuck the same way stating fetching and then retries and then timeout. already apps launched earlier before upgrading too were stating the same error. when I ping the npm and yarn services they are reachable and very well online. something went wrong immediately after the upgrade. please look

Inside Environment we should use PASSWORD_HASH, instead of password.

I had problems with .env file being added and removed to the gitignore and the repo by mistake, now everytime i need to rebuild nixpacks fails to pull changes due to changes on the repo on the server (namely .env file created by the environment tab) I was able to fix it by opening the server console and going to /etc/easypanel/projects/my-project/my-service/code and running git checkout -- .env to discard "local" changes to the file then the deployment would succeed. It's solved for me but maybe provide it as an option for everyone else or include this in the documentation

When i import a snapshot file, i can create services with forbidden name formats. When i try to delete them i got a invalid name bad request.

The version that easypanel is installing from dify is 0.8.3 and the current one is already at 0.11.3 and it is not possible to update. We need correction on this.

I am experiencing an issue with managing a few specific Cloudflare tunnels in my EasyPanel instance. These particular tunnels cannot be edited or deleted through the EasyPanel interface. When I attempt these actions, the network console shows a 404 error, even though the tunnels still exist in Cloudflare. I have also tried deleting these tunnels directly from Cloudflare, but after some time, they reappear in Cloudflare without any action on my part, while they never disappear from EasyPanel. It's important to note that this issue only affects a few specific tunnels, not all of them. I would appreciate your assistance in resolving this issue. Thank you in advance. { "error": { "json": { "message": "Request failed with status code 404", "code": -32603, "data": { "code": "INTERNAL_SERVER_ERROR", "httpStatus": 500, "path": "cloudflareTunnel.deleteTunnelRule", "zodErrors": null } } } }

I've been testing the native integration with Cloudflare tunnels in the new version 1.55.0, but there is a small bug. Apparently, when you create a new "Cloudflare Tunnel Rule" in a domain you must always enter a subdomain, otherwise the response gives a 400 error. Looking at the EasyPanel logs, it seems that the request made to Cloudflare is always sent "<subdomain>.<domain>", so if the subdomain is empty ".<domain>" is sent and the Cloudflare API responds with a 400. Otherwise the integration works wonderfully well.

the fault domain does not work at all. i am unable to access any of the apps or services with the given domain or when i try to link a new one. the page just gets stuck in a never ending loading rampage until it decides to throw me a 404 page or could not connect

I am trying to use nodejs 20 but when I deploy it doesnt accept the value. I mentioned nodejs_20 to be used in nix packages but it always fails. there is no documentation for it too. please suggest an alternative to use nodejs_20 in nixpack