sujiba / docker-ownDynDNS-netcup

1 stars 0 forks source link

Fatal error: Uncaught RuntimeException #1

Open nillebor opened 1 week ago

nillebor commented 1 week ago

I created your image. Unfortunately, I get the following error message when calling the update page: `Fatal error: Uncaught RuntimeException: .env file missing in /var/www/html/update.php:15 Stack trace:

0 {main}

thrown in /var/www/html/update.php on line 15`

I have to enter the update URL directly in the browser it User, Pass, Domain. With subdomain and IP. Both have the same problem.

I wanted to move the installation from my own web server to Docker. That .env file is the same. The file is also recognized and after deletion the container does not start because the file is missing.

Do you have any advice?

sujiba commented 1 week ago

Hi,

what does your docker-compose.yml look like? Have you mounted the config from this repo under /var/www/html/ownDynDNS/.env?

nillebor commented 1 week ago

I useyour compose Volume: - ./config:/var/www/html/ownDynDNS/.env and config-file (tested config and .env) is right

sujiba commented 1 week ago

I've made some changes in the past without pushing them to this repo. Could you try again building the container with the new Dockerfile?

nillebor commented 1 week ago

Sorry for the late reply. I had to test a lot.

I have tested some. The problem is the config. config > .env does not work. The file is not displayed in the container! config > config or netcup.env > netcup.env works. .env only does not work. That will be up to Docker. This is also probably the reason why other developers use Environments or other configs. But this container needs them .env.

Tested on DSM 7.2.2 from Synology

Wouldn't a nginx server be smaller? The Apache makes another mistake here. Whether this also affects ownDynDNS, I can not say at the moment.

AH00094: Command line: 'apache2 -D FOREGROUND' [mpm_prefork:notice] [pid 1:tid 1] AH00163: Apache/2.4.62 (Debian) PHP/8.3.12 configured -- resuming normal operations AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.19.0.2. Set the 'ServerName' directive globally to suppress this message