search

coollabsio / coolify

An open-source & self-hostable Heroku / Netlify / Vercel alternative.
https://coolify.io
Apache License 2.0
31.73k stars 1.63k forks source link

[Bug]: various v4 beta install issues #1109

Closed spencerflagg closed 3 months ago

spencerflagg commented 1 year ago

Installing 4.0.0-beta.12 on a fresh Ubuntu 22.10 VM.

Installation needs sudo su

Running the installation one-liner throws the error "Please run as root", and running with sudo throws the same error. Needed to run sudo su to get it to work.

Issues installing docker

The first time the installation script completed, it seemed to fail installing Docker, but displayed a "completed" message anyway. Here's what the terminal showed:

-------------
Welcome to Coolify v4 beta installer!
This script will install everything for you.
(Source code: https://github.com/coollabsio/coolify/blob/main/scripts/install.sh)

-------------
OS: ubuntu 22.10
Coolify version: 4.0.0-beta.12
-------------
Installing required packages...
Docker is not installed. Installing Docker...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 21734  100 21734    0     0  42065      0 --:--:-- --:--:-- --:--:-- 42120
# Executing docker install script, commit: a8a6b338bdfedd7ddefb96fe3e7fe7d4036d945a
+ sh -c apt-get update -qq >/dev/null
+ sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq apt-transport-https ca-certificates curl >/dev/null
E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 3577 (unattended-upgr)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Docker installed successfully
-------------
Check Docker Configuration...
jq: error: Could not open file /etc/docker/daemon.json.original-20230623-133634: No such file or directory
Docker configuration updated, restart docker daemon...
Failed to restart docker.service: Unit docker.service not found.
-------------
Downloading required files from CDN...
/data/coolify/source/upgrade.sh: line 18: docker: command not found

Congratulations! Your Coolify instance is ready to use.

Please visit http://77.175.38.180:8000 to get started.

Docker was not installed at this point. (I checked by running docker ps.)

However, I immediately ran the one-liner once more, and this time Docker was successfully installed, and the containers were running correctly.

IP vs Localhost

On my particular setup, http://x.x.x.x:8000 does not resolve in the browser, but localhost:8000 does. Perhaps both links can be displayed?

Tytan-Codes commented 1 year ago

I also got an error:

Welcome to Coolify v4 beta installer!
This script will install everything for you.
(Source code: https://github.com/coollabsio/coolify/blob/main/scripts/install.sh)

-------------
OS: ubuntu 22.04
Coolify version: 4.0.0-beta.14
-------------
Installing required packages...
-------------
Check Docker Configuration...
Docker configuration is up to date.
-------------
Downloading required files from CDN...
latest: Pulling from coollabsio/coolify-builder
Digest: sha256:f2d783d5660e709a9001c53167ea9404e1db8314aab9483875773771a32091c3
Status: Image is up to date for ghcr.io/coollabsio/coolify-builder:latest
redis Pulling
coolify Pulling
postgres Pulling
redis Pulled
postgres Pulled
coolify Pulled
Network coolify  Creating
Network coolify  Created
Volume "coolify-db"  Creating
Volume "coolify-db"  Created
Volume "coolify-redis"  Creating
Volume "coolify-redis"  Created
Container coolify-redis  Creating
Container coolify-db  Creating
Container coolify-redis  Created
Container coolify-db  Created
Container coolify  Creating
Container coolify  Created
Container coolify-db  Starting
Container coolify-redis  Starting
Container coolify-db  Started
Container coolify-redis  Started
Container coolify-db  Waiting
Container coolify-redis  Waiting
Container coolify-db  Healthy
Container coolify-redis  Healthy
Container coolify  Starting
Error response from daemon: driver failed programming external connectivity on endpoint coolify (452ca7ce63deadf837a695583c5f5369d14278f608c1686bbcf1cdf47111b656): Bind for 0.0.0.0:8000 failed: port is already allocated

Congratulations! Your Coolify instance is ready to use.

(I took out my ip)

I already ran these commands to unallocated them butttttt. Its still not working.

sudo lsof -i :8000
sudo kill <PID>
sudo lsof -i :8000

That command showed that everything was working soooooooo.

andrasbacsai commented 1 year ago

Installing 4.0.0-beta.12 on a fresh Ubuntu 22.10 VM.

Installation needs sudo su

Running the installation one-liner throws the error "Please run as root", and running with sudo throws the same error. Needed to run sudo su to get it to work.

Issues installing docker

The first time the installation script completed, it seemed to fail installing Docker, but displayed a "completed" message anyway. Here's what the terminal showed:

-------------
Welcome to Coolify v4 beta installer!
This script will install everything for you.
(Source code: https://github.com/coollabsio/coolify/blob/main/scripts/install.sh)

-------------
OS: ubuntu 22.10
Coolify version: 4.0.0-beta.12
-------------
Installing required packages...
Docker is not installed. Installing Docker...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 21734  100 21734    0     0  42065      0 --:--:-- --:--:-- --:--:-- 42120
# Executing docker install script, commit: a8a6b338bdfedd7ddefb96fe3e7fe7d4036d945a
+ sh -c apt-get update -qq >/dev/null
+ sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq apt-transport-https ca-certificates curl >/dev/null
E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 3577 (unattended-upgr)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Docker installed successfully
-------------
Check Docker Configuration...
jq: error: Could not open file /etc/docker/daemon.json.original-20230623-133634: No such file or directory
Docker configuration updated, restart docker daemon...
Failed to restart docker.service: Unit docker.service not found.
-------------
Downloading required files from CDN...
/data/coolify/source/upgrade.sh: line 18: docker: command not found

Congratulations! Your Coolify instance is ready to use.

Please visit http://77.175.38.180:8000 to get started.

Docker was not installed at this point. (I checked by running docker ps.)

However, I immediately ran the one-liner once more, and this time Docker was successfully installed, and the containers were running correctly.

IP vs Localhost

On my particular setup, http://x.x.x.x:8000 does not resolve in the browser, but localhost:8000 does. Perhaps both links can be displayed?

I try to reproduce the issue.

andrasbacsai commented 1 year ago

I also got an error:

Welcome to Coolify v4 beta installer!
This script will install everything for you.
(Source code: https://github.com/coollabsio/coolify/blob/main/scripts/install.sh)

-------------
OS: ubuntu 22.04
Coolify version: 4.0.0-beta.14
-------------
Installing required packages...
-------------
Check Docker Configuration...
Docker configuration is up to date.
-------------
Downloading required files from CDN...
latest: Pulling from coollabsio/coolify-builder
Digest: sha256:f2d783d5660e709a9001c53167ea9404e1db8314aab9483875773771a32091c3
Status: Image is up to date for ghcr.io/coollabsio/coolify-builder:latest
redis Pulling
coolify Pulling
postgres Pulling
redis Pulled
postgres Pulled
coolify Pulled
Network coolify  Creating
Network coolify  Created
Volume "coolify-db"  Creating
Volume "coolify-db"  Created
Volume "coolify-redis"  Creating
Volume "coolify-redis"  Created
Container coolify-redis  Creating
Container coolify-db  Creating
Container coolify-redis  Created
Container coolify-db  Created
Container coolify  Creating
Container coolify  Created
Container coolify-db  Starting
Container coolify-redis  Starting
Container coolify-db  Started
Container coolify-redis  Started
Container coolify-db  Waiting
Container coolify-redis  Waiting
Container coolify-db  Healthy
Container coolify-redis  Healthy
Container coolify  Starting
Error response from daemon: driver failed programming external connectivity on endpoint coolify (452ca7ce63deadf837a695583c5f5369d14278f608c1686bbcf1cdf47111b656): Bind for 0.0.0.0:8000 failed: port is already allocated

Congratulations! Your Coolify instance is ready to use.

(I took out my ip)

I already ran these commands to unallocated them butttttt. Its still not working.

sudo lsof -i :8000
sudo kill <PID>
sudo lsof -i :8000

That command showed that everything was working soooooooo.

It is because something is already running on port 8000. I will add a check in the installation script!

Tytan-Codes commented 1 year ago

I also got an error:

Welcome to Coolify v4 beta installer!
This script will install everything for you.
(Source code: https://github.com/coollabsio/coolify/blob/main/scripts/install.sh)

-------------
OS: ubuntu 22.04
Coolify version: 4.0.0-beta.14
-------------
Installing required packages...
-------------
Check Docker Configuration...
Docker configuration is up to date.
-------------
Downloading required files from CDN...
latest: Pulling from coollabsio/coolify-builder
Digest: sha256:f2d783d5660e709a9001c53167ea9404e1db8314aab9483875773771a32091c3
Status: Image is up to date for ghcr.io/coollabsio/coolify-builder:latest
redis Pulling
coolify Pulling
postgres Pulling
redis Pulled
postgres Pulled
coolify Pulled
Network coolify  Creating
Network coolify  Created
Volume "coolify-db"  Creating
Volume "coolify-db"  Created
Volume "coolify-redis"  Creating
Volume "coolify-redis"  Created
Container coolify-redis  Creating
Container coolify-db  Creating
Container coolify-redis  Created
Container coolify-db  Created
Container coolify  Creating
Container coolify  Created
Container coolify-db  Starting
Container coolify-redis  Starting
Container coolify-db  Started
Container coolify-redis  Started
Container coolify-db  Waiting
Container coolify-redis  Waiting
Container coolify-db  Healthy
Container coolify-redis  Healthy
Container coolify  Starting
Error response from daemon: driver failed programming external connectivity on endpoint coolify (452ca7ce63deadf837a695583c5f5369d14278f608c1686bbcf1cdf47111b656): Bind for 0.0.0.0:8000 failed: port is already allocated

Congratulations! Your Coolify instance is ready to use.

(I took out my ip)

I already ran these commands to unallocated them butttttt. Its still not working.

sudo lsof -i :8000
sudo kill <PID>
sudo lsof -i :8000

That command showed that everything was working soooooooo.

It is because something is already running on port 8000. I will add a check in the installation script!

Thanks!

letto4135 commented 1 year ago

On a brand new Linode with update/upgrade ran I get

root@localhost:~# curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash
-------------
Welcome to Coolify v4 beta installer!
This script will install everything for you.
(Source code: https://github.com/coollabsio/coolify/blob/main/scripts/install.sh)

-------------
OS: ubuntu 22.04
Coolify version: 4.0.0-beta.15
-------------
Installing required packages...
-------------
Check Docker Configuration...
Docker configuration is up to date.
-------------
Downloading required files from CDN...
latest: Pulling from coollabsio/coolify-builder
4db1b89c0bd1: Pull complete 
4b7f64e032ba: Pull complete 
98c6fda82b07: Pull complete 
9fb6b0021485: Pull complete 
028c8a1dfef9: Pull complete 
4f4fb700ef54: Pull complete 
Digest: sha256:f2d783d5660e709a9001c53167ea9404e1db8314aab9483875773771a32091c3
Status: Downloaded newer image for ghcr.io/coollabsio/coolify-builder:latest
 redis Pulling 
 coolify Pulling 
 postgres Pulling 
 coolify Error 
 redis Error 
 postgres Error 
Error response from daemon: manifest unknown

Congratulations! Your Coolify instance is ready to use.

Not sure why it can't find what its looking for here...

 redis Pulling 
 coolify Pulling 
 postgres Pulling 
 coolify Error 
 redis Error 
 postgres Error 
Error response from daemon: manifest unknown
gkibria commented 1 year ago

On a brand new Linode with update/upgrade ran I get

root@localhost:~# curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash
-------------
Welcome to Coolify v4 beta installer!
This script will install everything for you.
(Source code: https://github.com/coollabsio/coolify/blob/main/scripts/install.sh)

-------------
OS: ubuntu 22.04
Coolify version: 4.0.0-beta.15
-------------
Installing required packages...
-------------
Check Docker Configuration...
Docker configuration is up to date.
-------------
Downloading required files from CDN...
latest: Pulling from coollabsio/coolify-builder
4db1b89c0bd1: Pull complete 
4b7f64e032ba: Pull complete 
98c6fda82b07: Pull complete 
9fb6b0021485: Pull complete 
028c8a1dfef9: Pull complete 
4f4fb700ef54: Pull complete 
Digest: sha256:f2d783d5660e709a9001c53167ea9404e1db8314aab9483875773771a32091c3
Status: Downloaded newer image for ghcr.io/coollabsio/coolify-builder:latest
 redis Pulling 
 coolify Pulling 
 postgres Pulling 
 coolify Error 
 redis Error 
 postgres Error 
Error response from daemon: manifest unknown

Congratulations! Your Coolify instance is ready to use.

Not sure why it can't find what its looking for here...

 redis Pulling 
 coolify Pulling 
 postgres Pulling 
 coolify Error 
 redis Error 
 postgres Error 
Error response from daemon: manifest unknown

Same error here on brand new ubuntu vps on Hetzner.

letto4135 commented 1 year ago

@gkibria I forgot I commented here, I did figure it out. Use this curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash -s next The name of the version is 'next' in the cdn, not 4.0.0-beta.15...

andrasbacsai commented 1 year ago

On a brand new Linode with update/upgrade ran I get

root@localhost:~# curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash
-------------
Welcome to Coolify v4 beta installer!
This script will install everything for you.
(Source code: https://github.com/coollabsio/coolify/blob/main/scripts/install.sh)

-------------
OS: ubuntu 22.04
Coolify version: 4.0.0-beta.15
-------------
Installing required packages...
-------------
Check Docker Configuration...
Docker configuration is up to date.
-------------
Downloading required files from CDN...
latest: Pulling from coollabsio/coolify-builder
4db1b89c0bd1: Pull complete 
4b7f64e032ba: Pull complete 
98c6fda82b07: Pull complete 
9fb6b0021485: Pull complete 
028c8a1dfef9: Pull complete 
4f4fb700ef54: Pull complete 
Digest: sha256:f2d783d5660e709a9001c53167ea9404e1db8314aab9483875773771a32091c3
Status: Downloaded newer image for ghcr.io/coollabsio/coolify-builder:latest
 redis Pulling 
 coolify Pulling 
 postgres Pulling 
 coolify Error 
 redis Error 
 postgres Error 
Error response from daemon: manifest unknown

Congratulations! Your Coolify instance is ready to use.

Not sure why it can't find what its looking for here...

 redis Pulling 
 coolify Pulling 
 postgres Pulling 
 coolify Error 
 redis Error 
 postgres Error 
Error response from daemon: manifest unknown

Maybe I'm wrong, but it looks like you are on an ARM server. It was not supported till 4.0.0-beta.15. The latest beta version (beta.16) supports ARM based servers as well.

andrasbacsai commented 1 year ago

@gkibria I forgot I commented here, I did figure it out. Use this curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash -s next The name of the version is 'next' in the cdn, not 4.0.0-beta.15...

The next version is super edge/staging version. It means that is equal if you are using development version. Only I use to test things out before releasing the production version to the wild. If you are brave enough, you can use it, but I do not recommend it. :)

letto4135 commented 1 year ago

@andrasbacsai I believe the problem was curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash pointed to 4.0.0-beta.15 which didn't exist in the packages until 4 hours ago meaning you had to use -s next to actually use 4.0.0-beta.15.

Geczy commented 1 year ago

is there an upgrade path from v3 to v4 yet?

ikbenignace commented 1 year ago

is there an upgrade path from v3 to v4 yet?

It's not worth upgrading yet since there is still a lot missing.

andrasbacsai commented 1 year ago

Is there an upgrade path from v3 to v4 yet?

There will be, but not with a simple button. 🙂

poipiii commented 1 year ago

I ran into 2 issues when installing beta 4.00-18

environment:

digital ocean droplet:

root@ubuntu-coolify-test:~# curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash
-------------
Welcome to Coolify v4 beta installer!
This script will install everything for you.
(Source code: https://github.com/coollabsio/coolify/blob/main/scripts/install.sh)

-------------
OS: ubuntu 22.04
Coolify version: 4.0.0-beta.18
-------------
Installing required packages...
-------------
Check Docker Configuration...
Docker configuration is up to date.
-------------
Downloading required files from CDN...
latest: Pulling from coollabsio/coolify-helper
Digest: sha256:bf5b666b107229a21912ae667a365af8af5dcb75eedc751b29f87cb97624c834
Status: Image is up to date for ghcr.io/coollabsio/coolify-helper:latest
 redis Pulling 
 coolify Pulling 
 postgres Pulling 
 coolify Pulled 
 redis Pulled 
 postgres Pulled 
time="2023-08-12T16:27:56Z" level=warning msg="volume \"coolify-db\" already exists but was not created for project \"app\". Use `external: true` to use an existing volume"
 Container coolify-redis  Recreate
 Container coolify-db  Recreate
 Container coolify-db  Recreated
 Container coolify-redis  Recreated
 Container coolify  Recreate
 Container coolify  Recreated
 Container coolify-db  Starting
 Container coolify-redis  Starting
 Container coolify-db  Started
 Container coolify-redis  Started
 Container coolify-redis  Waiting
 Container coolify-db  Waiting
 Container coolify-db  Error
 Container coolify-redis  Healthy
dependency failed to start: container coolify-db is unhealthy

Congratulations! Your Coolify instance is ready to use.

Please visit http://xxx.xxx.xxx.xxx:8000 to get started.
root@ubuntu-coolify-test:~# docker ps
CONTAINER ID   IMAGE                               COMMAND                  CREATED          STATUS                         PORTS                                       NAMES
f97c7426178c   postgres:15-alpine                  "docker-entrypoint.s…"   15 seconds ago   Restarting (1) 4 seconds ago                                               coolify-db
9a1f3d0c9394   redis:alpine                        "docker-entrypoint.s…"   15 seconds ago   Up 13 seconds (healthy)        6379/tcp                                    coolify-redis
b93364c5f752   cll85tqx70002mjado2gqbtti:51d625a   "docker-entrypoint.s…"   55 minutes ago   Up 5 minutes                   0.0.0.0:5000->3000/tcp, :::5000->3000/tcp   cll85tqx70002mjado2gqbtti

@andrasbacsai

ThallesP commented 1 year ago

@andrasbacsai Maybe I'm wrong but when piping the curl output to bash, it's creating an unprivileged shell? It should be curl -fsSL https://cdn.coollabs.io/coolify/install.sh | sudo bash I remember coolify v3 was like that.

andrasbacsai commented 1 year ago

Yes, you are right. The bash needs sudo to have privileged shell.

Yurgeman commented 10 months ago

@andrasbacsai

I can't install coolify 

root@yurgeman:~# curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash
-------------
Welcome to Coolify v4 beta installer!
This script will install everything for you.
(Source code: https://github.com/coollabsio/coolify/blob/main/scripts/install.sh)

-------------
OS: ubuntu 22.04
Coolify version: 4.0.0-beta.119
-------------
Installing required packages...
-------------
Check Docker Configuration...
Docker configuration is up to date.
-------------
Downloading required files from CDN...
2768bcbd9e2dadf2da0d4f05044ffc5ae483961035ac9eeba6020a1544e95b27
latest: Pulling from coollabsio/coolify-helper
*****
 5a7f4c369a39 Download complete 
 af9cc04be135 Extracting [==============================================>    ]  33.42MB/36.23MB
 af9cc04be135 Extracting [================================================>  ]  35.39MB/36.23MB
 af9cc04be135 Extracting [==================================================>]  36.23MB/36.23MB
failed to register layer: unlinkat /usr/share/doc/adduser/examples/adduser.local.conf.examples: invalid argument

Congratulations! Your Coolify instance is ready to use.

Please visit http://x.x.x.x:8000 to get started.
root@yurgeman:~# docker ps
CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES
root@yurgeman:~#

sys info:

root@yurgeman:~# lscpu
Architecture:           aarch64
  CPU op-mode(s):       32-bit, 64-bit
  Byte Order:           Little Endian
CPU(s):                 128
  On-line CPU(s) list:  4,23,36,55,67,94
  Off-line CPU(s) list: 0-3,5-22,24-35,37-54,56-66,68-93,95-127
Vendor ID:              ARM
  Model name:           Neoverse-N1
    Model:              1
    Thread(s) per core: 1
    Core(s) per socket: 128
    Socket(s):          1
    Stepping:           r3p1
    Frequency boost:    disabled
    CPU max MHz:        3000.0000
    CPU min MHz:        1000.0000
    BogoMIPS:           50.00
    Flags:              fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp 
                        asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
Caches (sum of all):    
  L1d:                  8 MiB (128 instances)
  L1i:                  8 MiB (128 instances)
  L2:                   128 MiB (128 instances)
NUMA:                   
  NUMA node(s):         1
  NUMA node0 CPU(s):    0-127
Vulnerabilities:        
  Itlb multihit:        Not affected
  L1tf:                 Not affected
  Mds:                  Not affected
  Meltdown:             Not affected
  Mmio stale data:      Not affected
  Retbleed:             Not affected
  Spec store bypass:    Mitigation; Speculative Store Bypass disabled via prctl
  Spectre v1:           Mitigation; __user pointer sanitization
  Spectre v2:           Mitigation; CSV2, BHB
  Srbds:                Not affected
  Tsx async abort:      Not affected
root@yurgeman:~#
almereyda commented 9 months ago

Here installing build 146 led to the postgres database being unhealthy for too long, which somehow stopped the script, so the coolify container remained in created state. Running docker start coolify was needed for it to get working on this Ubuntu 22.04 machine.

One observation is, that when a job repeatingly fails, e.g. due to a local network condition, it cannot write into its log.

  2023-11-26 02:22:01 App\Notifications\TransactionalEmails\Test .... 56s FAIL

In StreamHandler.php line 137:

  The stream or file "/var/www/html/storage/logs/laravel.log" could not be op  
  ened in append mode: Failed to open stream: Permission denied                
  The exception occurred while attempting to log: The stream or file "/var/ww  
  w/html/storage/logs/laravel.log" could not be opened in append mode: Failed  
   to open stream: Permission denied                                           
  The exception occurred while attempting to log: Connection could not be est  
  ablished with host "mail.example.com:587": stream_socket_client(): Unable  
   to connect to mail.example.com:587 (Cannot assign requested address)      
  Context: {"exception":{}}                                                    
  Context: {"exception":{}}                                                    

  2023-11-26 02:22:04 App\Notifications\TransactionalEmails\Test ..... RUNNING
  2023-11-26 02:22:04 App\Notifications\TransactionalEmails\Test . 9.58ms FAIL

In StreamHandler.php line 137:

  The stream or file "/var/www/html/storage/logs/laravel.log" could not be op  
  ened in append mode: Failed to open stream: Permission denied                
  The exception occurred while attempting to log: The stream or file "/var/ww  
  w/html/storage/logs/laravel.log" could not be opened in append mode: Failed  
   to open stream: Permission denied                                           
  The exception occurred while attempting to log: Illuminate\Mail\MailManager  
  ::getConfig(): Argument #1 ($name) must be of type string, null given, call  
  ed in /var/www/html/vendor/laravel/framework/src/Illuminate/Mail/MailManage  
  r.php on line 111                                                            
  Context: {"exception":{}}                                                    
  Context: {"exception":{}}

I don't know what the second error means.

Also it appears the Coolify application is not receiving or not reacting to the X-Forwarded-For HTTP header, since it is showing the IP address of the coolify-proxy for incoming bot scans:

2023/11/26 02:03:15 [error] 153#153: *530 access forbidden by rule, client: 172.18.0.5, server: _, request: "GET /.vscode/sftp.json HTTP/1.1", host: "apps.example.com"           
2023/11/26 02:03:16 [error] 153#153: *530 access forbidden by rule, client: 172.18.0.5, server: _, request: "GET /.DS_Store HTTP/1.1", host: "apps.example.com"                   
2023/11/26 02:03:16 [error] 153#153: *530 access forbidden by rule, client: 172.18.0.5, server: _, request: "GET /.env HTTP/1.1", host: "apps.example.com"                        
2023/11/26 02:03:16 [error] 153#153: *530 access forbidden by rule, client: 172.18.0.5, server: _, request: "GET /.git/config HTTP/1.1", host: "apps.example.com"                 
2023/11/26 02:04:49 [error] 154#154: *605 access forbidden by rule, client: 172.18.0.5, server: _, request: "GET /.git/config HTTP/1.1", host: "apps.example.com"

Additionally Coolify creates RSA keys in https://apps.example.com/security/private-key/new

It would be favourable to default to ED25519 keys here, and to only offer RSA as a fallback option for legacy clients. The keys also look much nicer.

andrasbacsai commented 3 months ago

A lot changed since, so I'm closing this one.

Mishatopkek commented 3 months ago

I still have the same issue as @poipiii 

mishafedora@fedora:~$ curl -fsSL https://cdn.coollabs.io/coolify/install.sh | sudo bash
[sudo] password for mishafedora: 
-------------
Welcome to Coolify v4 beta installer!
This script will install everything for you.
(Source code: https://github.com/coollabsio/coolify/blob/main/scripts/install.sh)

-------------
OS: fedora 40
Coolify version: 4.0.0-beta.294
-------------
Installing required packages...
###############################################################################
WARNING: Could not detect if OpenSSH server is installed and running - this does not mean that it is not installed, just that we could not detect it.
Please make sure it is set, otherwise Coolify cannot connect to the host system. 

###############################################################################
###############################################################################
WARNING: PermitRootLogin is not enabled in /etc/ssh/sshd_config.
It is set to N/A (commented out or not found at all). Should be prohibit-password, yes or without-password.

Please make sure it is set, otherwise Coolify cannot connect to the host system. 

###############################################################################
-------------
Check Docker Configuration...
Docker configuration is up to date.
-------------
Downloading required files from CDN...
/data/coolify/source/upgrade.sh: line 16: openssl: command not found
/data/coolify/source/upgrade.sh: line 20: openssl: command not found
/data/coolify/source/upgrade.sh: line 24: openssl: command not found
 Container coolify-redis  Recreate
 Container coolify-db  Recreate
 Container coolify-realtime  Recreate
 Container coolify-db  Recreated
 Container coolify-redis  Recreated
 Container coolify  Recreate
 Container coolify  Recreated
 Container coolify-realtime  Recreated
 Container coolify-db  Starting
 Container coolify-realtime  Starting
 Container coolify-redis  Starting
 Container coolify-db  Started
 Container coolify-redis  Started
 Container coolify-redis  Waiting
 Container coolify-db  Waiting
 Container coolify-realtime  Started
 Container coolify-db  Error
 Container coolify-redis  Error
dependency failed to start: container coolify-db is unhealthy
Mishatopkek commented 3 months ago

Here's some extra information

mishafedora@fedora:~$ sudo docker logs coolify-db
Error: Database is uninitialized and superuser password is not specified.
       You must specify POSTGRES_PASSWORD to a non-empty value for the
       superuser. For example, "-e POSTGRES_PASSWORD=password" on "docker run".

       You may also use "POSTGRES_HOST_AUTH_METHOD=trust" to allow all
       connections without a password. This is *not* recommended.

       See PostgreSQL documentation about "trust":
       https://www.postgresql.org/docs/current/auth-trust.html
mishafedora@fedora:~$ sudo docker logs coolify-redis

*** FATAL CONFIG FILE ERROR (Redis 7.2.5) ***
Reading the configuration file, at line 4
>>> 'requirepass'
wrong number of arguments
Dev-Love-Per-byte commented 3 months ago

root@fedora:/home/kumar# curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash

Welcome to Coolify v4 beta installer! This script will install everything for you. (Source code: https://github.com/coollabsio/coolify/blob/main/scripts/install.sh )

OS: fedora 40 Coolify version: 4.0.0-beta.297

Installing required packages... OpenSSH server is installed. PermitRootLogin is enabled.

Check Docker Configuration... Docker configuration is up to date.

Downloading required files from CDN... Container coolify-db Recreate Container coolify-realtime Recreate Container coolify-redis Recreate Container coolify-redis Recreated Container coolify-db Recreated Container coolify Recreate Container coolify Recreated Container coolify-realtime Recreated Container coolify-db Starting Container coolify-redis Starting Container coolify-realtime Starting Container coolify-db Started Container coolify-redis Started Container coolify-db Waiting Container coolify-redis Waiting Container coolify-realtime Started Container coolify-db Error Container coolify-redis Error dependency failed to start: container coolify-db is unhealthy

i do also get the same problem

Dev-Love-Per-byte commented 3 months ago

All you have edit that file

############################################################################### WARNING: PermitRootLogin is not enabled in /etc/ssh/sshd_config. It is set to N/A (commented out or not found at all). Should be prohibit-password, yes or without-password.

and uncomment the PermitRootLogin

Mishatopkek commented 3 months ago

I have another problem and I'm not sure how it's related. I get Error: root@host.docker.internal: Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). I uncommented PermitRootLogin and set to yes and tried prohibit-password. Each time I restarted the service. Still doesn't work

Dev-Love-Per-byte commented 3 months ago

I have another problem and I'm not sure how it's related. I get Error: root@host.docker.internal: Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). I uncommented PermitRootLogin and set to yes and tried prohibit-password. Each time I restarted the service. Still doesn't work

Try Manual method it works for me

For me that the commands provided in the documentation are not creating the required directories. So i created the directories manually by following these steps:

  1. Open a terminal on your Fedora system.

  2. Switch to the root user by running the following command:

sudo su
  1. Create the main /data/coolify directory:
mkdir /data/coolify
  1. Navigate to the /data/coolify directory:
cd /data/coolify
  1. Create the following subdirectories inside /data/coolify:
mkdir source
mkdir ssh
mkdir applications
mkdir databases
mkdir backups
mkdir services
mkdir proxy
mkdir webhooks-during-maintenance
  1. Create the subdirectories inside /data/coolify/ssh:
mkdir ssh/keys
mkdir ssh/mux
  1. Create the subdirectory inside /data/coolify/proxy:
mkdir proxy/dynamic

After executing these commands, you should have the following directory structure:

/data/coolify
├── applications
├── backups
├── databases
├── proxy
│   └── dynamic
├── services
├── source
├── ssh
│   ├── keys
│   └── mux
└── webhooks-during-maintenance

If you encounter any permission issues while creating these directories, you may need to run the commands with sudo or as the root user.

Once you have created the required directories manually, you can proceed with the remaining steps in the Coolify manual installation guide.

Manually 1

SSH Enabled

Make sure SSH is enabled and you can connect to your server with SSH from your local machine with root user: more details here. 2

Curl Installed

Make sure curl command is available on your server. 3

Install Docker Engine (24+)

Follow the official documentation to install Docker Engine on your server: Docker Engine Installation. 4

Create Directories

Create the base configuration directories under /data/coolify.

mkdir -p /data/coolify/{source,ssh,applications,databases,backups,services,proxy,webhooks-during-maintenance} mkdir -p /data/coolify/ssh/{keys,mux} mkdir -p /data/coolify/proxy/dynamic

5

Generate SSH Key

Generate an SSH key for Coolify to be able to manage this server from itself.

ssh-keygen -f /data/coolify/ssh/keys/id.root@host.docker.internal -t ed25519 -N '' -C root@coolify

6

Setup Your SSH Key

Add your public SSH key to ~/.ssh/authorized_keys. This will allow Coolify to connect to this server from itself.

cat /data/coolify/ssh/keys/id.root@host.docker.internal.pub >>~/.ssh/authorized_keys chmod 600 ~/.ssh/authorized_keys

You can skip this step if you already have an SSH key. But you need to add this key to your Coolify instance after installation. 7

Setup Configuration Files

Copy the docker-compose.yml, docker-compose.prod.yml, .env.production & upgrade.sh files from Coolify’s CDN to /data/coolify/source.

curl -fsSL https://cdn.coollabs.io/coolify/docker-compose.yml -o /data/coolify/source/docker-compose.yml curl -fsSL https://cdn.coollabs.io/coolify/docker-compose.prod.yml -o /data/coolify/source/docker-compose.prod.yml curl -fsSL https://cdn.coollabs.io/coolify/.env.production -o /data/coolify/source/.env curl -fsSL https://cdn.coollabs.io/coolify/upgrade.sh -o /data/coolify/source/upgrade.sh

8

Set Permissions

Set permissions for all the files and directories.

chown -R 9999:root /data/coolify chmod -R 700 /data/coolify

9

Generate Values

Generate values for the following variables in /data/coolify/source/.env.

sed -i "s|APP_ID=.|APP_ID=$(openssl rand -hex 16)|g" /data/coolify/source/.env sed -i "s|APP_KEY=.|APP_KEY=base64:$(openssl rand -base64 32)|g" /data/coolify/source/.env sed -i "s|DB_PASSWORD=.|DB_PASSWORD=$(openssl rand -base64 32)|g" /data/coolify/source/.env sed -i "s|REDIS_PASSWORD=.|REDIS_PASSWORD=$(openssl rand -base64 32)|g" /data/coolify/source/.env sed -i "s|PUSHER_APP_ID=.|PUSHER_APP_ID=$(openssl rand -hex 32)|g" /data/coolify/source/.env sed -i "s|PUSHER_APP_KEY=.|PUSHER_APP_KEY=$(openssl rand -hex 32)|g" /data/coolify/source/.env sed -i "s|PUSHER_APP_SECRET=.*|PUSHER_APP_SECRET=$(openssl rand -hex 32)|g" /data/coolify/source/.env

This only needs to be done once, when you install Coolify for the first time. If you do it after Coolify has been started, it will break your installation.

Make sure you save the values somewhere. If you lose them, you will lose access to your Coolify installation and all your data. 10

Default Docker Network

Make sure the default coolify Docker network is available.

docker network create --attachable coolify

11

Start Coolify

docker compose --env-file /data/coolify/source/.env -f /data/coolify/source/docker-compose.yml -f /data/coolify/source/docker-compose.prod.yml up -d --pull always --remove-orphans --force-recreate

12

Open Coolify's UI

Now you can access Coolify on port http://:8000 of your server.

Mishatopkek commented 2 months ago

Sorry for the long reply @Dev-Love-Per-byte , but i have this error image

cjgaliana commented 2 months ago

I algo got the same error dependency failed to start: container coolify-redis is unhealthy

I tried to recreate the docker volumes but nothing. Any clue?

Mishatopkek commented 2 months ago

I algo got the same error dependency failed to start: container coolify-redis is unhealthy

I tried to recreate the docker volumes but nothing. Any clue?

Try to check this file data/coolify/source/.env. This file contains all secrets, if something is empty, you should fill it the proper way

cjgaliana commented 2 months ago

Good news... I followed all the steps for uninstalling (https://coolify.io/docs/uninstall) and then it worked. Thanks!