Upgrading 0.15.2 to 0.15.3 breaks all functionality

kmanwar89 commented 1 month ago

Environment

Docker

Version

0.15.2 & 0.15.3

Describe the problem

I've been using 0.15.2 - no issues. Noticed an update was available from within the manage dashboard function, so I did a quick docker-compose pull, and brought the container back up.

At this point, the logs (shown below) began spamming with [next-auth][error][CLIENT_FETCH_ERROR] messages.

I brought the container down, manually pinned the version to 0.15.2 ad brought it back up. This let me go back through the username/password process (which I shouldn't have had to, since I already had a user configured?) but I can't get back into the admin dashboard due to the same errors seen below.

c3dcce675f7f appears to be my container ID, but I'm not sure why it's showing these messages.

Logs

❯ up <------- running docker compose up -d [+] Running 1/1 ✔ Container homarr Started 10.5s ❯ logs homarr | 2024-05-14T23:23:25.779756012Z Exporting hostname... homarr | 2024-05-14T23:23:25.779808119Z Migrating database... homarr | 2024-05-14T23:23:25.907351283Z yarn run v1.22.19 homarr | 2024-05-14T23:23:25.928875332Z $ ts-node ./migrate.ts homarr | 2024-05-14T23:23:27.574195069Z Done in 1.67s. homarr | 2024-05-14T23:23:27.595580466Z Starting production server... homarr | 2024-05-14T23:23:28.551237444Z Listening on port 7575 url: http://e9daa4814ce8:7575

homarr | 2024-05-14T23:23:40.405402582Z TypeError: fetch failed homarr | 2024-05-14T23:23:40.405463070Z at Object.fetch (/app/node_modules/next/dist/compiled/undici/index.js:1:26669) homarr | 2024-05-14T23:23:40.405472779Z at process.processTicksAndRejections (node:internal/process/task_queues:95:5) homarr | 2024-05-14T23:23:40.405481790Z at async getServerSideProps (/app/.next/server/pages/manage/about.js:828:26) { homarr | 2024-05-14T23:23:40.405489333Z cause: ConnectTimeoutError: Connect Timeout Error homarr | 2024-05-14T23:23:40.405497995Z at onConnectTimeout (/app/node_modules/next/dist/compiled/undici/index.js:1:82152) homarr | 2024-05-14T23:23:40.405506167Z at /app/node_modules/next/dist/compiled/undici/index.js:1:81644 homarr | 2024-05-14T23:23:40.405513710Z at Immediate._onImmediate (/app/node_modules/next/dist/compiled/undici/index.js:1:82034) homarr | 2024-05-14T23:23:40.405521743Z at process.processImmediate (node:internal/timers:478:21) { homarr | 2024-05-14T23:23:40.405529426Z code: 'UND_ERR_CONNECT_TIMEOUT' homarr | 2024-05-14T23:23:40.405538157Z } homarr | 2024-05-14T23:23:40.405545631Z } homarr | 2024-05-14T23:23:43.081350718Z TypeError: fetch failed homarr | 2024-05-14T23:23:43.081415118Z at Object.fetch (/app/node_modules/next/dist/compiled/undici/index.js:1:26669) homarr | 2024-05-14T23:23:43.081426573Z at process.processTicksAndRejections (node:internal/process/task_queues:95:5) homarr | 2024-05-14T23:23:43.081435584Z at async getServerSideProps (/app/.next/server/pages/manage/about.js:828:26) { homarr | 2024-05-14T23:23:43.081445153Z cause: ConnectTimeoutError: Connect Timeout Error homarr | 2024-05-14T23:23:43.081453814Z at onConnectTimeout (/app/node_modules/next/dist/compiled/undici/index.js:1:82152) homarr | 2024-05-14T23:23:43.081463244Z at /app/node_modules/next/dist/compiled/undici/index.js:1:81644 homarr | 2024-05-14T23:23:43.081472743Z at Immediate._onImmediate (/app/node_modules/next/dist/compiled/undici/index.js:1:82034) homarr | 2024-05-14T23:23:43.081481474Z at process.processImmediate (node:internal/timers:478:21) { homarr | 2024-05-14T23:23:43.081490485Z code: 'UND_ERR_CONNECT_TIMEOUT' homarr | 2024-05-14T23:23:43.081499495Z } homarr | 2024-05-14T23:23:43.081507108Z } homarr | 2024-05-14T23:23:45.943092290Z [next-auth][error][CLIENT_FETCH_ERROR] homarr | 2024-05-14T23:23:45.943146143Z https://next-auth.js.org/errors#client_fetch_error fetch failed { homarr | 2024-05-14T23:23:45.943156621Z error: { homarr | 2024-05-14T23:23:45.943165561Z message: 'fetch failed', homarr | 2024-05-14T23:23:45.943203768Z stack: 'TypeError: fetch failed\n' + homarr | 2024-05-14T23:23:45.943213407Z ' at Object.fetch (/app/node_modules/next/dist/compiled/undici/index.js:1:26669)\n' + homarr | 2024-05-14T23:23:45.943222837Z ' at process.processTicksAndRejections (node:internal/process/task_queues:95:5)', homarr | 2024-05-14T23:23:45.943231428Z name: 'TypeError' homarr | 2024-05-14T23:23:45.943240089Z }, homarr | 2024-05-14T23:23:45.943248681Z url: 'http://e9daa4814ce8:7575/api/auth/session', homarr | 2024-05-14T23:23:45.943257132Z message: 'fetch failed' homarr | 2024-05-14T23:23:45.943265793Z }

After reverting versions (ignore the ERRCONREFUSED - those containers haven't been reconfigured yet):

❯ down <---- docker compose down command [+] Running 1/1 ✔ Container homarr Removed 10.2s ❯ dcps NAME IMAGE COMMAND SERVICE CREATED STATUS PORTS ❯ l Permissions Size User Date Modified Name drwxr-xr-x - USERNAME 24 Mar 21:42 homarr .rw-r--r-- 699 USERNAME 12 May 15:32 docker-compose.yml ❯ p <---- editing the compose file to specify the image version # ❯ up [+] Running 1/1 ✔ homarr Pulled 0.4s [+] Running 1/1 ✔ Container homarr Started 0.3s ❯ logs homarr | 2024-05-14T23:26:42.513385056Z Exporting hostname... homarr | 2024-05-14T23:26:42.513441424Z Migrating database... homarr | 2024-05-14T23:26:42.643077472Z yarn run v1.22.19 homarr | 2024-05-14T23:26:42.665441434Z $ ts-node ./migrate.ts homarr | 2024-05-14T23:26:44.343211314Z Done in 1.71s. homarr | 2024-05-14T23:26:44.364719988Z Starting production server... homarr | 2024-05-14T23:26:45.307807076Z Listening on port 7575 url: http://c3dcce675f7f:7575 homarr | 2024-05-14T23:26:54.365757851Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:26:54.366418333Z ℹ Database is writeable homarr | 2024-05-14T23:27:04.540502567Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:27:04.540533162Z ℹ Database is writeable homarr | 2024-05-14T23:27:14.685710181Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:27:14.686241613Z ℹ Database is writeable homarr | 2024-05-14T23:27:24.852258744Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:27:24.852613521Z ℹ Database is writeable homarr | 2024-05-14T23:27:34.994403747Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:27:34.995901432Z ℹ Database is writeable homarr | 2024-05-14T23:27:45.148994538Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:27:45.149382283Z ℹ Database is writeable homarr | 2024-05-14T23:27:48.164260833Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:27:49.166579831Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:27:55.281766924Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:27:55.283045271Z ℹ Database is writeable homarr | 2024-05-14T23:28:05.416464863Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:28:05.416946067Z ℹ Database is writeable homarr | 2024-05-14T23:28:15.560790449Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:28:15.561886341Z ℹ Database is writeable homarr | 2024-05-14T23:28:25.674749903Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:28:25.674791325Z ℹ Database is writeable homarr | 2024-05-14T23:28:35.796538244Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:28:36.799709233Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... ^Ccanceled ❯ logs homarr | 2024-05-14T23:26:42.513385056Z Exporting hostname... homarr | 2024-05-14T23:26:42.513441424Z Migrating database... homarr | 2024-05-14T23:26:42.643077472Z yarn run v1.22.19 homarr | 2024-05-14T23:26:42.665441434Z $ ts-node ./migrate.ts homarr | 2024-05-14T23:26:44.343211314Z Done in 1.71s. homarr | 2024-05-14T23:26:44.364719988Z Starting production server... homarr | 2024-05-14T23:26:45.307807076Z Listening on port 7575 url: http://c3dcce675f7f:7575 homarr | 2024-05-14T23:26:54.365757851Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:26:54.366418333Z ℹ Database is writeable homarr | 2024-05-14T23:27:04.540502567Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:27:04.540533162Z ℹ Database is writeable homarr | 2024-05-14T23:27:14.685710181Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:27:14.686241613Z ℹ Database is writeable homarr | 2024-05-14T23:27:24.852258744Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:27:24.852613521Z ℹ Database is writeable homarr | 2024-05-14T23:27:34.994403747Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:27:34.995901432Z ℹ Database is writeable homarr | 2024-05-14T23:27:45.148994538Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:27:45.149382283Z ℹ Database is writeable homarr | 2024-05-14T23:27:48.164260833Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:27:49.166579831Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:27:55.281766924Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:27:55.283045271Z ℹ Database is writeable homarr | 2024-05-14T23:28:05.416464863Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:28:05.416946067Z ℹ Database is writeable homarr | 2024-05-14T23:28:15.560790449Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:28:15.561886341Z ℹ Database is writeable homarr | 2024-05-14T23:28:25.674749903Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:28:25.674791325Z ℹ Database is writeable homarr | 2024-05-14T23:28:35.796538244Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:28:36.799709233Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:28:45.928354375Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:28:45.928399639Z ℹ Database is writeable homarr | 2024-05-14T23:28:56.041614631Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:28:56.041735332Z ℹ Database is writeable homarr | 2024-05-14T23:29:06.179137353Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:29:06.179449934Z ℹ Database is writeable homarr | 2024-05-14T23:29:16.313129660Z ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... homarr | 2024-05-14T23:29:16.313296044Z ℹ Database is writeable homarr | 2024-05-14T23:29:20.033639158Z user USERNAME is trying to log in. checking password... homarr | 2024-05-14T23:29:20.146078484Z user USERNAME successfully authorized homarr | 2024-05-14T23:29:25.705320263Z ℹ Local icons repository directory exists and contains 0 icons homarr | 2024-05-14T23:29:25.926890809Z homarr | 2024-05-14T23:29:25.926942289Z ERROR Unexpected response: connect ECONNREFUSED 192.168.1.10:9011 homarr | 2024-05-14T23:29:25.926952696Z homarr | 2024-05-14T23:29:25.928553526Z homarr | 2024-05-14T23:29:25.928591176Z ERROR Unexpected response: connect ECONNREFUSED 192.168.1.10:9012 homarr | 2024-05-14T23:29:25.928601653Z homarr | 2024-05-14T23:29:25.929642004Z homarr | 2024-05-14T23:29:25.929673017Z ERROR Unexpected response: connect ECONNREFUSED 192.168.1.10:9004 homarr | 2024-05-14T23:29:25.929683006Z homarr | 2024-05-14T23:29:25.930468054Z homarr | 2024-05-14T23:29:25.930499067Z ERROR Unexpected response: connect ECONNREFUSED 192.168.1.10:9009 homarr | 2024-05-14T23:29:25.930511291Z homarr | 2024-05-14T23:29:25.931151050Z homarr | 2024-05-14T23:29:25.931177733Z ERROR Unexpected response: connect ECONNREFUSED 192.168.1.10:9003 homarr | 2024-05-14T23:29:25.931189119Z homarr | 2024-05-14T23:29:25.931784802Z homarr | 2024-05-14T23:29:25.931810717Z ERROR Unexpected response: connect ECONNREFUSED 192.168.1.10:9001 homarr | 2024-05-14T23:29:25.931822452Z homarr | 2024-05-14T23:29:25.932443840Z homarr | 2024-05-14T23:29:25.932470942Z ERROR Unexpected response: connect ECONNREFUSED 192.168.1.10:9007 homarr | 2024-05-14T23:29:25.932504820Z homarr | 2024-05-14T23:29:25.933047068Z homarr | 2024-05-14T23:29:25.933073331Z ERROR Unexpected response: connect ECONNREFUSED 192.168.1.10:9005 homarr | 2024-05-14T23:29:25.933084857Z homarr | 2024-05-14T23:29:25.933682636Z homarr | 2024-05-14T23:29:25.933694161Z ERROR Unexpected response: connect ECONNREFUSED 192.168.1.10:9006 homarr | 2024-05-14T23:29:25.933704569Z homarr | 2024-05-14T23:29:35.713080607Z homarr | 2024-05-14T23:29:35.713135510Z ERROR Failed to fetch icons from repository 'GitHub': TypeError: fetch failed homarr | 2024-05-14T23:29:35.713146826Z homarr | 2024-05-14T23:29:35.713383478Z homarr | 2024-05-14T23:29:35.713408275Z ERROR Failed to fetch icons from repository 'UnPkg': TypeError: fetch failed homarr | 2024-05-14T23:29:35.713419800Z homarr | 2024-05-14T23:29:35.714567999Z homarr | 2024-05-14T23:29:35.714598314Z ERROR Failed to fetch icons from repository 'JsDelivr': TypeError: fetch failed homarr | 2024-05-14T23:29:35.714609350Z homarr | 2024-05-14T23:29:36.390243216Z [next-auth][error][CLIENT_FETCH_ERROR] homarr | 2024-05-14T23:29:36.390294486Z https://next-auth.js.org/errors#client_fetch_error fetch failed { homarr | 2024-05-14T23:29:36.390304475Z error: { homarr | 2024-05-14T23:29:36.390315022Z message: 'fetch failed', homarr | 2024-05-14T23:29:36.390323544Z stack: 'TypeError: fetch failed\n' + homarr | 2024-05-14T23:29:36.390332554Z ' at Object.fetch (/app/node_modules/next/dist/compiled/undici/index.js:1:26669)\n' + homarr | 2024-05-14T23:29:36.390341775Z ' at process.processTicksAndRejections (node:internal/process/task_queues:95:5)', homarr | 2024-05-14T23:29:36.390350296Z name: 'TypeError' homarr | 2024-05-14T23:29:36.390358818Z }, homarr | 2024-05-14T23:29:36.390367899Z url: 'http://c3dcce675f7f:7575/api/auth/session', homarr | 2024-05-14T23:29:36.390376560Z message: 'fetch failed' homarr | 2024-05-14T23:29:36.390384593Z } homarr | 2024-05-14T23:29:36.717788096Z homarr | 2024-05-14T23:29:36.717867306Z ERROR Failed to fetch icons from repository 'JsDelivr': TypeError: fetch failed homarr | 2024-05-14T23:29:36.717880578Z homarr | 2024-05-14T23:29:37.850711296Z [next-auth][error][CLIENT_FETCH_ERROR] homarr | 2024-05-14T23:29:37.850751530Z https://next-auth.js.org/errors#client_fetch_error fetch failed { homarr | 2024-05-14T23:29:37.850760959Z error: { homarr | 2024-05-14T23:29:37.850769551Z message: 'fetch failed', homarr | 2024-05-14T23:29:37.850778073Z stack: 'TypeError: fetch failed\n' + homarr | 2024-05-14T23:29:37.850786804Z ' at Object.fetch (/app/node_modules/next/dist/compiled/undici/index.js:1:26669)\n' + homarr | 2024-05-14T23:29:37.850820681Z ' at process.processTicksAndRejections (node:internal/process/task_queues:95:5)', homarr | 2024-05-14T23:29:37.850829552Z name: 'TypeError' homarr | 2024-05-14T23:29:37.850837725Z }, homarr | 2024-05-14T23:29:37.850845478Z url: 'http://c3dcce675f7f:7575/api/auth/session', homarr | 2024-05-14T23:29:37.850854000Z message: 'fetch failed' homarr | 2024-05-14T23:29:37.850861963Z } homarr | 2024-05-14T23:29:37.914229673Z homarr | 2024-05-14T23:29:37.914265576Z ERROR Ping timed out for app with id '9af44446-dc6d-4545-9b25-565828ff077f' in config 'default' -> url: https://path.domain.com) homarr | 2024-05-14T23:29:37.914276542Z homarr | 2024-05-14T23:29:37.915236284Z homarr | 2024-05-14T23:29:37.915257169Z ERROR Ping timed out for app with id '88e8cd6f-4319-4168-b949-3913597359a0' in config 'default' -> url: https://path.domain.com) homarr | 2024-05-14T23:29:37.915267787Z homarr | 2024-05-14T23:29:37.917896600Z homarr | 2024-05-14T23:29:37.917920768Z ERROR Ping timed out for app with id '5931e744-9539-4e9b-80a7-c7dba39b7031' in config 'default' -> url: https://homarr.dev) homarr | 2024-05-14T23:29:37.917930477Z homarr | 2024-05-14T23:29:37.918992760Z homarr | 2024-05-14T23:29:37.919013994Z ERROR Ping timed out for app with id '2ecd624e-5c96-4421-af4c-0fe311dd61aa' in config 'default' -> url: https://drawio:8443) homarr | 2024-05-14T23:29:37.919024053Z homarr | 2024-05-14T23:29:37.919850451Z homarr | 2024-05-14T23:29:37.919871336Z ERROR Ping timed out for app with id '1beebb2a-7d9f-4b8a-9789-5296611986ad' in config 'default' -> url: https://homarr.dev) homarr | 2024-05-14T23:29:37.919883420Z homarr | 2024-05-14T23:29:41.312745573Z [next-auth][error][CLIENT_FETCH_ERROR] homarr | 2024-05-14T23:29:41.312800894Z https://next-auth.js.org/errors#client_fetch_error fetch failed { homarr | 2024-05-14T23:29:41.312812280Z error: { homarr | 2024-05-14T23:29:41.312821361Z message: 'fetch failed', homarr | 2024-05-14T23:29:41.312830022Z stack: 'TypeError: fetch failed\n' + homarr | 2024-05-14T23:29:41.312838544Z ' at Object.fetch (/app/node_modules/next/dist/compiled/undici/index.js:1:26669)\n' + homarr | 2024-05-14T23:29:41.312847065Z ' at process.processTicksAndRejections (node:internal/process/task_queues:95:5)', homarr | 2024-05-14T23:29:41.312855797Z name: 'TypeError' homarr | 2024-05-14T23:29:41.312864388Z }, homarr | 2024-05-14T23:29:41.312872351Z url: 'http://c3dcce675f7f:7575/api/auth/session', homarr | 2024-05-14T23:29:41.312880873Z message: 'fetch failed' homarr | 2024-05-14T23:29:41.312888487Z }

Context

Successfully using 0.15.2, decide to upgrade to 0.15.3 (because upgrades are good, right?) and the above-described behavior began. Absolutely 0 issues using 0.15.2 previously. No other environment changes made - this behavior only began after the upgrade.

Please tick the boxes

[X] I confirm that I attached the proper logs
[X] I've read the docs
[X] I've checked for duplicate issues
[X] I've tried to debug myself

kmanwar89 commented 1 month ago

I completely deleted my containers and the homarr folder and re-created it - this would be the equivalent of a from-scratch environment. I pinned the image to 0.15.2 and I'm still seeing the error logs in my docker compose logs. If they're inconsequential, I can ignore them, but I guess now I'm curious what is actually causing the behavior...docker compose log below for reference:

#---------------------------------------------------------------------
#                Homarr -  A homepage for your server.                
#---------------------------------------------------------------------
services:
  homarr:
    image: ghcr.io/ajnart/homarr:0.15.2
    container_name: homarr
    restart: unless-stopped
    volumes:
      - ./homarr/configs:/app/data/configs
      - ./homarr/icons:/app/public/icons
      - /var/run/docker.sock:/var/run/docker.sock
    networks:
      - npm_service

networks:
  npm_service:
    name: npm_service
    external: true

kmanwar89 commented 1 month ago

Behavior is still present in 0.15.1, this is weird. Everything initially appears just fine, but as soon as I start clicking around in the management functions, the UI becomes less responsive and then suddenly starts throwing these logs.

SeDemal commented 1 month ago

You're missing the mount for the user database (data). I'm surprised this even worked for v0.15.2. Since you didn't have a mount for it, it also explains why the database didn't persist and you had to go through onboarding again. As long as the permissions for those mounts are correctly done, you should be able to go right ahead and go directly to the latest tag again. https://homarr.dev/docs/getting-started/installation#installation

ajnart commented 1 month ago

You're missing the mount for the user database (data). I'm surprised this even worked for v0.15.2. Since you didn't have a mount for it, it also explains why the database didn't persist and you had to go through onboarding again. As long as the permissions for those mounts are correctly done, you should be able to go right ahead and go directly to the latest tag again. https://homarr.dev/docs/getting-started/installation#installation

You should be able to use homarr without a database, docker will automatically create a volume for homarr (because of the VOLUME argument in the Dockerfile), it should be persistent across updates

ajnart commented 1 month ago

homarr | 2024-05-14T23:29:36.390367899Z url: 'http://c3dcce675f7f:7575/api/auth/session', homarr | 2024-05-14T23:29:36.390376560Z message: 'fetch failed'

This error indicates that the server cannot access :7575 for some reason and thus cannot accept the user. My idea is that this error happens because you had a DB that was not successfully migrated or died for some reason in the volume created by docker, when deleting the container the volume will stay for some time and auto-delete after a while. @kmanwar89 Try something along the lines of docker (compose) volume prune after removing the container then re-create it. Or you can mount a user db like @SeDemal suggesed

kmanwar89 commented 1 month ago

homarr | 2024-05-14T23:29:36.390367899Z url: 'http://c3dcce675f7f:7575/api/auth/session', homarr | 2024-05-14T23:29:36.390376560Z message: 'fetch failed'

This error indicates that the server cannot access :7575 for some reason and thus cannot accept the user. My idea is that this error happens because you had a DB that was not successfully migrated or died for some reason in the volume created by docker, when deleting the container the volume will stay for some time and auto-delete after a while. @kmanwar89 Try something along the lines of docker (compose) volume prune after removing the container then re-create it. Or you can mount a user db like @SeDemal suggesed

Hey thanks for the answer. I went through manually pruning volumes, though they weren't named, and I didn't capture which container they were bound to:

I also completely brought down the container (command used was docker compose down --rmi all -v):

I also deleted the homarr folder in my docker-compose directory, just to be sure:

Bringing the container up is fine - this is before opening it in my browser:

(The logs repeat)

I open the browser, go to my user icon --> manage -- > start clicking on items on the left, and specifically it seems if I click "docker' then the same error logs continue. I'll follow up this post with a screen recording displaying the behavior

kmanwar89 commented 1 month ago

I think the behavior is very obvious in the screen recording - I started completely from scratch including deleting the docker image, pruning volumes, using the compose file from the website (the version: tag is depricated now, just FYI) and bringing the container up. Everything works until you open the manage page. Happy to grab any more evidence that might be helpful for diagnosis and troubleshooting, thanks!

Image version pulled was 0.15.3 (latest docker tag)

https://github.com/ajnart/homarr/assets/11323060/c00e5b8e-2218-4eda-a80f-58d322af97d9

I just tested and seeing same behavior in 0.15.2, so that's a bit unexpected, but at least the pages eventually load. I'll keep testing versions and if it's broken on every single version, I'll take another look something specific to my machine (which is really, really strange)

After some time of those errors appearing in the log, this error page shows up (with no usable details):

kmanwar89 commented 1 month ago

Video showing behavior on 0.15.2

https://github.com/ajnart/homarr/assets/11323060/21bab06d-4cee-40dc-86f8-1bb9fe8533d1

SeDemal commented 1 month ago

I'd say possible communication/network issue, Have you tried not putting it behind a reverse proxy? Check that it works at all without outside factors first.

kmanwar89 commented 1 month ago

I'd say possible communication issue, Have you tried not putting it behind a reverse proxy? Check that it works at all without outside factors first.

Whats odd is iit has always been behind a reverse proxy, as i'm self-hosting and don't have a public IP. I'm using cloudflare tunnels + reverse proxy to achieve a communication path.

I'm testing on a totally separate device (Pi 4) as a test - initially testing, with no reverse proxy, default config file taken straight from Homarr's website) and 0.15.1 works fine. Testing with the latest, 0.15.3, also works fine. I'm drilling down into this further - The only thing I "changed" was upgrading - everything else remained the same.

kmanwar89 commented 1 month ago

I replicated my setup on my Pi 4 - Homarr behind NPM, identical compose files, no other containers running on either machine - works on the Pi4 without issue, still faces that same error on my production server. This is rather perplexing. I guess it's something specific to my prod server, but I can't figure out what is different between the two from a configuration perspective. I'll keep poking around...

kmanwar89 commented 1 month ago

Testing again, few hours later, and the issue appears to have self-resolved -- did I get plagued by some CDN funkiness, maybe?

SeDemal commented 1 month ago

So everything is working now? Remember to keep the data mount if you want your user database to permeate and enjoy v0.15.3 :)

kmanwar89 commented 1 month ago

Seems to be good so far; I honestly can't explain why I faced this behavior, but I can't appear to re-create it either - makes me glad I recorded those screen recordings when I did!

I'll close this for the time being - hopefully it was just a fluke that we can blame on intergalactic gremlins or some such!

ajnart commented 1 month ago

Seems like a very strange issue. I think all software is bound to have some amount of flakiness. I think that your browser/pc tried to request to the auth server when it was down and the DNS saved the answer as a failure

ajnart / homarr