[Bug]: Non-root user breaks proxy

[Bilge]

Error Message and Logs

When changing proxy type:

Error: bash: line 2: cd: /data/coolify/proxy/caddy: Permission denied

Steps to Reproduce

1. Install Coolify as non-root user with sudo access.
2. Try to change proxy.

Example Repository URL

No response

Coolify Version

v4.0.0-beta.367

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 22.04.3 LTS

Additional Information

Initially these directories are provisioned with the correct 9999:0 permissions, but it seems Coolify (ab)uses its sudo access to set the wrong permissions when provisioning the proxy.

/data/coolify# ll

total 40
drwx------ 10    9999 root    4096 Nov 12 14:12 ./
drwx------  3    9999 root    4096 Nov 12 14:12 ../
drwx------  2    9999 root    4096 Nov 12 14:12 applications/
drwx------  2    9999 root    4096 Nov 12 14:12 backups/
drwx------  2    9999 root    4096 Nov 12 14:12 databases/
drwx------  4 coolify coolify 4096 Nov 12 14:17 proxy/
drwx------  2    9999 root    4096 Nov 12 14:12 services/
drwx------  2    9999 root    4096 Nov 12 14:12 source/
drwx------  4    9999 root    4096 Nov 12 14:13 ssh/
drwx------  2    9999 root    4096 Nov 12 14:12 webhooks-during-maintenance/

Even manually resetting the permissions for this directory has no effect, since Coolify is constantly overwriting them with incorrect ownership, to such an extent that it is actually impossible to start the Caddy proxy at all with a non-root user.

[ddekkers]

@Bilge The error seems to refer to the parent directory. Changing owner and their permissions for /data/coolify solved the issue for me:

sudo chown -R 9999:NON_ROOT_USER /data/coolify
sudo chmod 750 /data/coolify

[Bilge]

Actually, it is correct to set non_root:non_root for every single directory except ssh (in complete defiance of what the setup readme claims).

[GauthierPLM]

I confirm this command works:

sudo chown -R NON_ROOT_USER:NON_ROOT_USER /data/coolify
sudo chmod 750 /data/coolify

Hoping to see this fixed soon. :)

[n0one42]

I confirm this command works:

sudo chown -R NON_ROOT_USER:NON_ROOT_USER /data/coolify
sudo chmod 750 /data/coolify

Hoping to see this fixed soon. :)

Fresh new ubuntu 24.04 server with a custom user with passwordless sudo

After doing so I get:

 Error: Unable to create a directory at /var/www/html/storage/app/ssh/mux. (View: /var/www/html/resources/views/components/server/navbar.blade.php) (View: /var/www/html/resources/views/components/server/navbar.blade.php) 

[AnonyMars]

same as @n0one42 ,

"Unable to create a directory at /var/www/html/storage/app/ssh/mux. (View: /var/www/html/resources/views/livewire/server/proxy/deploy.blade.php)"

[AnonyMars]

Oh @ddekkers was right on this :

sudo chown -R 9999:NON_ROOT_USER /data/coolify
sudo chmod 750 /data/coolify

My user is called coolify so :

sudo chown -R 9999:coolify /data/coolify
sudo chmod 750 /data/coolify

[piscis]

Oh @ddekkers was right on this :
...
My user is called coolify so :

sudo chown -R 9999:coolify /data/coolify sudo chmod 750 /data/coolify

That almost worked for me. However, after I switched from a root-based ssh login to a user-based login, my database backups suddenly stopped working due to permission issues with the database folder.

Example:

bash: line 2: /data/coolify/backups/databases/XXX-0/XXX-AAAA-BBBB-vg04wg84kk88o84c4wsoo4w4/pg-dump-AAAA-db-1737787114.dmp: Permission denied

To fix this, I recursively changed the permissions on the /data/coolify folder like so:

sudo chown -R 9999:coolify/data/coolify
sudo chmod -R 750 /data/coolify
sudo chmod -R 700 /data/coolify/ssh

I also noticed that in the self installation guide (9. https://coolify.io/docs/installation/ ) the manual states that you have to apply:

sudo chmod -R 700 /data/coolify

Which could be a problem if you go with a non root based setup for your servers because then backups dont have access to write to /data/coolify/backups/*. If you just sudo chmod -R 750 /data/coolify then your ssh keys inside of /data/coolify/ssh are to open and every secondary server will fail to validate and coolify will lose connection.

[MarArMar]

I fixed this and #2410 by ensuring all folders are created and with the right accesses :

CF https://coolify.io/docs/installation#_1-create-directories

sudo mkdir -p /data/coolify/{source,ssh,applications,databases,backups,services,proxy,webhooks-during-maintenance}
sudo mkdir -p /data/coolify/ssh/{keys,mux}
sudo mkdir -p /data/coolify/proxy/dynamic
sudo chown -R 9999:NON_ROOT_USER /data/coolify
sudo chmod -R 750 /data/coolify
sudo chmod -R 700 /data/coolify/ssh

[fs-99]

Any reasons why #4255 (comment) might not be the best solution?
Can we somehow help coolify make non-root user as a feature possible?
To me it seems like the best flow might be:
install script -> ui now accessible -> login -> root user y/n -> no: textfield for username
and then probably also somewhere allow ssh passphrase

[isasmendiagus]

So, the "correct" way to install coolify is as root ?