latest version brought back 404 on mobile Home Screen and authentication is not functioning

[fate8383]

Environment

Self-Hosted (Docker)

System

safari latest stable, linux rpi latest stable, docker latest stable

Version

Dashy version 2.1.1

Describe the problem

#628 like previous I raised this issue, and it was resolved with changing routing mode to HASH, but latest version again broke it, either history nor hash mode fixes it. Also noticed authentication is broken, no matter what browser I tried with cleared cache it goes right to the dashboard without any login.

Additional info

No response

Please tick the boxes

• You have explained the issue clearly, and included all relevant info
• You are using a supported version of Dashy
• You've checked that this issue hasn't already been raised
• You've checked the docs and troubleshooting guide
• You agree to the code of conduct

[psychowood]

I believe this is related to manifest.json having "start_url": "./index.html".

In my configuration (docker, macvlan network, caddy as reverse proxy), browsing directly to /index.html gives the very same error with a redirect to /404.

Again, I'm not sure if this is a workaround just for my conf, but changing start_url to "./" (in /app/public/manifest.json inside the container itself) and restarting fixes the problem. At least, up to the next image pull :)

[wolflarson]

Your comment about authentication being broken also applies to my issue #1019

Perhaps one is a duplicate. Downgrading to 2.1.0 fixed my auth issue for now.

[Dacred]

Changing "start_url" to "./" in /public/manifest.json and running yarn build fixes this issue(and #1019) for me as well.
Just restarting didn't work for me.

[liss-bot]

This issue has gone 6 weeks without an update. To keep the ticket open, please indicate that it is still relevant in a comment below. Otherwise it will be closed in 5 working days.

[kieraneglin]

#1026 Resolves this

[liss-bot]

This issue has gone 6 weeks without an update. To keep the ticket open, please indicate that it is still relevant in a comment below. Otherwise it will be closed in 5 working days.

[liss-bot]

This issue was automatically closed because it has been stalled for over 6 weeks with no activity.