H
Homarr23h ago
Mx

v1 Beta - Cannot use Reverse Proxy

Connecting directly to the host:port - Works fine. Connecting via hostname using reverse proxy: Page shows:
Application error: a server-side exception has occurred (see the server logs for more information).

Digest: 3570798718
Application error: a server-side exception has occurred (see the server logs for more information).

Digest: 3570798718
Logs show:
2024-12-18T02:19:01.918Z info: tRPC request from unknown by user 'undefined (undefined)'
2024-12-18T02:19:01.920Z info: tRPC request from server-fetch by user 'undefined (undefined)'
2024-12-18T02:19:01.925Z info: tRPC request from server-fetch by user 'undefined (undefined)'
2024-12-18T02:19:01.942Z info: tRPC request from rsc by user 'undefined (undefined)'
2024-12-18T02:19:01.944Z warn: No home board found
i [TRPCError]: UNAUTHORIZED
at /app/apps/nextjs/.next/server/chunks/9388.js:1:1654
at d (/app/apps/nextjs/.next/server/chunks/358.js:4:74)
at t (/app/apps/nextjs/.next/server/chunks/358.js:1:46619)
at /app/apps/nextjs/.next/server/chunks/358.js:4:1630
at async f (/app/apps/nextjs/.next/server/chunks/8531.js:1:6354) {
cause: undefined,
code: 'UNAUTHORIZED',
digest: '3570798718'
2024-12-18T02:19:01.918Z info: tRPC request from unknown by user 'undefined (undefined)'
2024-12-18T02:19:01.920Z info: tRPC request from server-fetch by user 'undefined (undefined)'
2024-12-18T02:19:01.925Z info: tRPC request from server-fetch by user 'undefined (undefined)'
2024-12-18T02:19:01.942Z info: tRPC request from rsc by user 'undefined (undefined)'
2024-12-18T02:19:01.944Z warn: No home board found
i [TRPCError]: UNAUTHORIZED
at /app/apps/nextjs/.next/server/chunks/9388.js:1:1654
at d (/app/apps/nextjs/.next/server/chunks/358.js:4:74)
at t (/app/apps/nextjs/.next/server/chunks/358.js:1:46619)
at /app/apps/nextjs/.next/server/chunks/358.js:4:1630
at async f (/app/apps/nextjs/.next/server/chunks/8531.js:1:6354) {
cause: undefined,
code: 'UNAUTHORIZED',
digest: '3570798718'
Cache cleared. Configuration worked on pre-1.0 homarr.
Solution:
I implemented a fix in https://github.com/homarr-labs/homarr/pull/1711 . Waiting for approval
Jump to solution
7 Replies
Cakey Bot
Cakey Bot23h ago
Thank you for submitting a support request. Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
❓ Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
Meierschlumpf
Meierschlumpf15h ago
This unauthorized error is only thrown when you open the boards page and are not logged in, created an issue for it on github
Solution
Manicraft1001
Manicraft100113h ago
I implemented a fix in https://github.com/homarr-labs/homarr/pull/1711 . Waiting for approval
Meierschlumpf
Meierschlumpf11h ago
Has been fixed in v1.0.0-beta.4
Mx
MxOP10h ago
Are all of those being pushed to the beta tag for the image, or is the new image under the tag above. I'm assuming the later as skopeo inspect says that beta.4 is also a tag
"RepoTags": [
"alpha",
"early-adopters",
"dev",
"v1.0.0-beta.1",
"beta",
"v1.0.0-beta.3",
"experimental-docker-permission-issue",
"fix-startup-permission-issue",
"v1.0.0-beta.4"
],
"RepoTags": [
"alpha",
"early-adopters",
"dev",
"v1.0.0-beta.1",
"beta",
"v1.0.0-beta.3",
"experimental-docker-permission-issue",
"fix-startup-permission-issue",
"v1.0.0-beta.4"
],
Meierschlumpf
Meierschlumpf10h ago
beta is where all betas are pushed, so you can either specify the specific 4 version or beta and run docker compose pull
Mx
MxOP10h ago
👍
Want results from more Discord servers?
Add your server