homarr: URI malformed

Environment

Docker

Version

No response

Describe the problem

I’ve used Homarr successfully for many months. I’m running it in Docker and running off the :latest tag. Today, the site isn’t accessible any longer. I’ve stopped the container, pulled the latest, restarted and the issue continues. I have deprecation errors in the long and an error about a malformed URI. I haven’t changed anything in the app in a few weeks, so I’m not sure what went wrong. Here is the error in the logs when I try to access the page. Any help is greatly appreciated!

root@fileserver:/docker/containers/homarr# docker logs -f homarr
Listening on port 7575 url: http://0b364d8056f5:7575
[DEPRECATED] default export is deprecated, instead import { create } from'zustand'
[DEPRECATED] default export is deprecated, instead import { create } from'zustand'
[DEPRECATED] default export is deprecated, instead import { create } from'zustand'
[DEPRECATED] default export is deprecated, instead import { create } from'zustand'
Error [URIError]: URI malformed
    at decodeURIComponent (<anonymous>)
    at parseCookieString (file:///app/.next/server/src/middleware.js:628:22)
    at new RequestCookies (file:///app/.next/server/src/middleware.js:678:28)
    at new NextRequest (file:///app/.next/server/src/middleware.js:851:22)
    at new NextRequestHint (file:///app/.next/server/src/middleware.js:1106:9)
    at adapter (file:///app/.next/server/src/middleware.js:1163:21)
    at next_middleware_loaderabsolutePagePath_private_next_root_dir_2Fsrc_2Fmiddleware_ts_page_2Fsrc_2Fmiddleware_rootDir_2Fhome_2Frunner_2Fwork_2Fhomarr_2Fhomarr_matchers_ (file:///app/.next/server/src/middleware.js:1313:18)
    at <unknown> (file:///app/node_modules/next/dist/server/web/sandbox/sandbox.js:73:30)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async NextNodeServer.runMiddleware (file:///app/node_modules/next/dist/server/next-server.js:1137:24)
TypeError: Cannot read properties of undefined (reading '_nextI18Next')
    at AppWithTranslation (/app/node_modules/next-i18next/dist/commonjs/appWithTranslation.js:92:29)
    at Wc (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:68:44)
    at Zc (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:253)
    at Z (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at Zc (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:481)
    at Z (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at $c (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
    at bd (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:77:404)
    at Z (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:217)
    at Zc (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:71:479)

Additional info

No response

Please tick the boxes

You’ve read the docs
You’ve checked for duplicate issues
You’ve tried to debug yourself

About this issue

Original URL
State: closed
Created a year ago
Comments: 19

Most upvoted comments

That is the fastest response I have ever received on any application issue. Thank you! I feel like an idiot not force clearing my cache first. That fixed the issue up for me. Thanks again for the speedy and thorough help and explanation of both issues!

rubylaser on Feb 12, 2023

Point of interest. I just got this message. Removed the docker image and pulled it again. App worked as expected.

tserversbfs on Mar 30, 2023

We don’t have an ETA on this. I am very busy at work currently, and don’t have time for this - sorry. @ajnart perhaps you could make a small 0.11.6 release for this?

If you can’t afford to wait, it’s recommend that you use the dev image.

manuel-rw on Mar 6, 2023

I run Authelia and SWAG in my environment. This new tag worked without issue for me across Chrome, Firefox, and Safari.

rubylaser on Feb 28, 2023

I am having the same problem as @benabhi. Using homarr docker image but in my case I access it through swag (not traeffik). I have tried using authelia or not with the same results. Clearing cache does not help. Accessing homarr directly in the internal IP (not through swag) does work. Let me know if I can provide any more info to help solving this issue.

jrhbcn on Feb 28, 2023