[Synology] Cant create a new board and preferences is blank
I am able to setup a board, but cant create a new one or access the preferences.
Solution:Jump to solution
Ok- I figured this out. I just needed to delete the homarr.syno.json file which Synology created.
25 Replies
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?
Here is my compose file
@Trader R. can you please add your server logs (you can of course remove any sensitive information like ips / domains if you want) Please also add the other missing data as requested from the app
Sure, here are the logs
I am using Windows 10
I am using image version 0.15.3
Thanks, I'll take a look
Is that all you get? Nothing about a 500 error as shown in the browser console?
Yes, these are the only logs I get from Portainer.
hm okay
Can you explain when the above errors happend (in the browser)?
all in all it looks like network configuration error to me. improper bridge, proxy, something. Did this issue appear after some time or is this after setting up, update maybe
this appeard right after setup
when I click on board, this is what I get. The rest of the bord works fine and I can access all external links fine.
You mean when you go to /board?
What do the logs look like when you open this page and can you check the server logs again. They must contain an error
Sure, see here.
Okay do you have configured the env variable
AUTH_LOGOUT_REDIRECT_URL?
Also: Are you logged in?Here are my env variables and yes, I am logged in.
Okay interessting...
Sadly I'm unable to reproduce anything in that direction...
that's a peculiar port configuration you got there. getting myself mixed up between 4755 and 7575
so, you are setting the internal port to stay 7575, but redirecting to 4755 outside the container. In that case nextauth_url cannot be of port 7575 since it's the address to be used externally.
I've successfully updated the ports to match and recreated the container. This action resolved the error messages previously appearing in the logs. However, I'm still encountering issues accessing the preferences and creating a second board. Despite the improvement in error reporting, these functionalities remain inaccessible
Just to make sure, those are services turned off or invalid right? or should they actually be accessible for communication?
@Trader R. does the error still happen if you set both ports to 7575 like the default config suggests ?
Yes it continues to happen. I updated the ports but the problem persists
Last thing I can think of is setting up host networking.
Somehow the connection gets cut off at some point, which is strange.
A proxy could also meddle with all of this, do you use anything of the likes? ngninx or traefik, vpn, tunnel
Thnks for trying to help. I dont use any proxy or anything. Its setup in a docker container.
Solution
Ok- I figured this out. I just needed to delete the homarr.syno.json file which Synology created.
Wow, great job finding it. Definitely would not have been able to guide you there then but I'm glad you found the issue. Thanks for sharing it too, in case someone else comes across it. Does everything work now?
Yes, everything is working now.