Unraid Docker installation on MySQL (webserver not available)

[Quaros]

I am trying to install Koillection via Docker on one of my Unraid servers. I am using MySQL as database. Both Koillection and MySQL are running but I am not able to reach the URL of the application in any way. In the GUI of Unraid I am using the following configuration:

The MySQL database has the following configuration:

Both Docker containers are running as can be seen in the following screenshot:

The Docker log of Koillection gives me the following information:

****` 1/11 - Make sure /uploads folders exist ****
**** 2/11 - Create the symbolic link for the /uploads folder ****
**** 3/11 - Setting env variables ****
**** 4/11 - Migrate the database ****
[notice] Migrating up to App\Migrations\Postgresql\Version20240906153414
[notice] Migration App\Migrations\Postgresql\Version20180731115129 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20181205142026 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20190307155057 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20190314154104 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20190403150430 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20190702133405 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20191003145915 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20191113104851 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20200411112345 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20200413120102 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20200414145453 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20200417113047 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20200418215133 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20200424103714 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20200425201544 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20200426100023 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20200727125257 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20200812165130 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20200923203222 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20201010130126 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20201215233838 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20210127105027 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20210514101359 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20211207190313 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20220205175140 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20220206175016 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20220208094033 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20220630095604 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20220701151517 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20220713065947 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20220716211147 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20220717133957 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20220722162446 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20220725195801 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20220829085105 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20220909073714 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20220916154614 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20220916220210 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20220918193105 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20220920140037 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20220922183031 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20221015171929 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20230317131449 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20230425130548 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20230519200850 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20230525083937 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20230613175143 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20230726072714 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20230801084644 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20230801125257 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20230803152739 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20231124104927 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20240105141323 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20240118222935 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20240204165839 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20240205153137 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20240329223202 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20240411083531 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] Migration App\Migrations\Postgresql\Version20240906153414 skipped during Execution. Reason: "Migration can only be executed safely on 'postgresql'."
[notice] finished in 24.8ms, used 14M memory, 59 migrations executed, 0 sql queries

 [OK] Successfully migrated to version:                                         
      App\Migrations\Postgresql\Version20240906153414                           


**** 5/11 - Create API keys ****

 [OK] Done!                                                                     

**** 6/11 - Refresh caches ****
Refreshing cached values for collections...
Refreshing cached values for wishlists...
Refreshing cached values for albums...
Done!
**** 7/11 - Create user and use PUID/PGID ****
-e      User UID :      1001
-e      User GID :      1001
**** 8/11 - Set Permissions ****
**** 9/11 - Create nginx log files ****
**** 10/11 - Create symfony log files ****
**** 11/11 - Setup complete, starting the server. ****

I am trying to reach the Koillection web application via: http://192.168.99.96:8737 but no connection can be made.
I am obviously doing something wrong here, but after some hours of troubleshooting I am still not any closer to a solution. Is there someone here who is able to help me with this?

[benjaminjonard]

Hello, sorry I don't know much about unraid.

The only thing I can think of is that on your last screenshot, the Koillection line indicates 172.17.0.5:8737/TCP -> ...
If that's supposed to work like docker port forwarding, it should be 172.17.0.5:80 as the Koillection container exposed the port 80

(Unless unraid uses a customized docker image, in that case I don't know :/)

[Quaros]

Thank you very much for your quick reply. Your suggestion fixed the issue. It seems that the Unraid Docker template contains the wrong port forwarding (8737 -> 8737) I removed the port field in the template and added it again with the correct port forwarding (80 -> 8738) and now it is working like a charm.