Easypanel not accessible on the internet

[yipfram]

### What is the problem ?
The problem is that my easypanel instance is not accessible on the internet. Each time I try to access to any domain connected to my instance (xxxxxx.easypanel.host OR/AND my custom domain pointing to my VPS ip) I face a 502 Bad gateway status code. In the developper tools, my request is loaded by my VPS but easypanel is not connecting it....
I tryied with a reverse proxy provided by cloudpanel. For 127.0.0.1:3000, everything works, but for any app, nothing works....

### What is my config ?
VPS hosted by hostinger
2Gb RAM, 1 heart CPU
OS : Ubuntu 22.04 , I also tried debian 11 always on new installs, with the commands displayed in the easypanel website guide(I litteraly did 20 different installs since yesterday....)

### What about logs ?
Traefik:
time="2023-07-27T20:40:39Z" level=info msg="Configuration loaded from flags." time="2023-07-27T20:40:40Z" level=error msg="Unable to append certificate /data/default-domain.crt to store: unable to generate TLS certificate : tls: failed to find any PEM data in certificate input" tlsStoreName=default time="2023-07-27T20:47:16Z" level=error msg="Unable to obtain ACME certificate for domains \"easypanel.xxxxxx.fr\": unable to generate a certificate for the domains [easypanel.xxxxx.fr]: acme: error: 429 :: POST :: https://acme-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rateLimited :: Error creating new order :: too many certificates (5) already issued for this exact set of domains in the last 168 hours: easypanel.xxxxxxxx.fr, retry after 2023-07-28T19:24:19Z: see [https://letsencrypt.org/docs/duplicate-certificate-limit/"](https://letsencrypt.org/docs/duplicate-certificate-limit/%22) rule="Host(easypanel.xxxxxx.fr)" providerName=letsencrypt.acme ACME CA="https://acme-v02.api.letsencrypt.org/directory" routerName=https-easypanel-domain@file time="2023-07-27T20:47:59Z" level=error msg="accept tcp [::]:8080: use of closed network connection" entryPointName=traefik time="2023-07-27T20:47:59Z" level=error msg="Error while starting server: accept tcp [::]:8080: use of closed network connection" entryPointName=traefik time="2023-07-27T20:47:59Z" level=error msg="accept tcp [::]:80: use of closed network connection" entryPointName=http time="2023-07-27T20:47:59Z" level=error msg="Error while starting server: accept tcp [::]:80: use of closed network connection" entryPointName=http time="2023-07-27T20:47:59Z" level=error msg="accept tcp [::]:443: use of closed network connection" entryPointName=https time="2023-07-27T20:47:59Z" level=error msg="Error while starting server: accept tcp [::]:443: use of closed network connection" entryPointName=https time="2023-07-27T20:48:11Z" level=info msg="Configuration loaded from flags."

Easypanel (from settings > Easypanel)
time="2023-07-27T20:40:39Z" level=info msg="Configuration loaded from flags." time="2023-07-27T20:40:40Z" level=error msg="Unable to append certificate /data/default-domain.crt to store: unable to generate TLS certificate : tls: failed to find any PEM data in certificate input" tlsStoreName=default time="2023-07-27T20:47:16Z" level=error msg="Unable to obtain ACME certificate for domains \"easypanel.romain-rochas.fr\": unable to generate a certificate for the domains [easypanel.romain-rochas.fr]: acme: error: 429 :: POST :: https://acme-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rateLimited :: Error creating new order :: too many certificates (5) already issued for this exact set of domains in the last 168 hours: easypanel.romain-rochas.fr, retry after 2023-07-28T19:24:19Z: see [https://letsencrypt.org/docs/duplicate-certificate-limit/"](https://letsencrypt.org/docs/duplicate-certificate-limit/%22) rule="Host(easypanel.romain-rochas.fr)" providerName=letsencrypt.acme ACME CA="https://acme-v02.api.letsencrypt.org/directory" routerName=https-easypanel-domain@file time="2023-07-27T20:47:59Z" level=error msg="accept tcp [::]:8080: use of closed network connection" entryPointName=traefik time="2023-07-27T20:47:59Z" level=error msg="Error while starting server: accept tcp [::]:8080: use of closed network connection" entryPointName=traefik time="2023-07-27T20:47:59Z" level=error msg="accept tcp [::]:80: use of closed network connection" entryPointName=http time="2023-07-27T20:47:59Z" level=error msg="Error while starting server: accept tcp [::]:80: use of closed network connection" entryPointName=http time="2023-07-27T20:47:59Z" level=error msg="accept tcp [::]:443: use of closed network connection" entryPointName=https time="2023-07-27T20:47:59Z" level=error msg="Error while starting server: accept tcp [::]:443: use of closed network connection" entryPointName=https time="2023-07-27T20:48:11Z" level=info msg="Configuration loaded from flags."

Something that may be involved :
When I try to deploy an app, here is what the logs dispays (the last line appears all the time):
WordPress not found in /var/www/html - copying now... WordPress not found in /var/www/html - copying now... WARNING: /var/www/html is not empty! (copying anyhow) Complete! WordPress has been successfully copied to /var/www/html No 'wp-config.php' found in /var/www/html, but 'WORDPRESS_...' variables supplied; copying 'wp-config-docker.php' (WORDPRESS_DB_HOST WORDPRESS_DB_NAME WORDPRESS_DB_PASSWORD WORDPRESS_DB_USER) Complete! WordPress has been successfully copied to /var/www/html AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 10.0.1.12. Set the 'ServerName' directive globally to suppress this message AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 10.0.1.13. Set the 'ServerName' directive globally to suppress this message AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 10.0.1.12. Set the 'ServerName' directive globally to suppress this message AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 10.0.1.13. Set the 'ServerName' directive globally to suppress this message [Thu Jul 27 21:01:04.310260 2023] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.56 (Debian) PHP/8.0.29 configured -- resuming normal operations [Thu Jul 27 21:01:04.318865 2023] [core:notice] [pid 1] AH00094: Command line: 'apache2 -D FOREGROUND' [Thu Jul 27 21:01:04.322974 2023] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.56 (Debian) PHP/8.0.29 configured -- resuming normal operations [Thu Jul 27 21:01:04.325461 2023] [core:notice] [pid 1] AH00094: Command line: 'apache2 -D FOREGROUND' [Thu Jul 27 21:01:06.668538 2023] [mpm_prefork:notice] [pid 1] AH00170: caught SIGWINCH, shutting down gracefully

nmap while my wordpress server was launched using easypanel:
`root@xxxxxx:~# nmap -sS localhost
Starting Nmap 7.80 ( https://nmap.org ) at 2023-07-27 21:06 UTC
Nmap scan report for localhost (127.0.0.1)
Host is up (0.0000040s latency).
Other addresses for localhost (not scanned): ::1
Not shown: 996 closed ports
PORT STATE SERVICE
22/tcp open ssh
80/tcp open http
443/tcp open https
3000/tcp open ppp

Nmap done: 1 IP address (1 host up) scanned in 0.03 seconds`

Don't hesitate to tell me if I forgot something...
And thank you in advance for your help ;)

[yipfram]

Sorry the logs render is aweful

[vinumweb]

This is what they said to me "Hostinger is not true virtualization and it fails since it is not possible to configure the kernel, swarm will not work."