Integrations not updating
Hi, I'm coming from the "old" Homarr which was really good. I've decided to try something new and go with Homarr version 1.0+. I've started without importing anything from my old instance.
Everything is now setup but the following integrations are not updating. I have to reload the page to force update the information gathered and it gets stuck, even the availability timer on the Proxmox integration is frozen.
- Weather
- Proxmox System Status
- Jellyseerr request list
- Tdarr
- Download clients (qbittorrent and Sabnzbd)
- Indexers status from Prowlarr
- Jellyfin (playing now)
I'm using version 1.27.0
Homarr is installed on a Proxmox LXC
I've tried using the IP and the domain behind NPM Plus reverse proxy.
I've tried with Edge, Brave and Chrome.
I've tried from different computers.
I always have the exact same behaviour: it's accurate when the page loads but then nothing is ever updated.
What could I provide to help find whats going on?
Solution:Jump to solution
Yeah as it says on the website and after creating an lxc it is on port 7575
26 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?
I've looked websocket in the network tab and it shows as "pending". It's the same thing accessing homarr with IP:port or domain name + reverse proxy.
Same behaviour using Edge, Chrome or Brave wether in normal or private browsing.
Hi, thanks for the post. I'm sorry that the new version isn't working for you yet. Can you post your details to https://discord.com/channels/972958686051962910/1391444568360226857 , since it's an already open post? We will likely create a GitHub issue for this since this needs further investigation.
Sorry, ignore my previous message. @Meierschlumpf do you have an idea?
For me it seems like redis can not be started because the port is already in use:
Could not create server TCP listening socket *:6379: bind: Address already in use
at least this is in your logsGood catch
But why is the port in use? Shouldn't the LXC be isolated? @CrazyWolf13
And perhaps we should implement a status indicator on Homarr and display an error message in the UI if redis is offline. Do you agree @Meierschlumpf ?
Yes would generally make sense for all internal "services"
Ok I will create a ticket
The lxc is definitely isolated, but maybe there is some stale service not fully excited.
Ahh I see the issue now, the startup scripts which is linked to the service starts redis too, reboot your lxc then 🙂
I think that's an issue on your reverse proxy then :/
Try without the reverse proxy please
Do you start Redis separately? If the right command is called, I think Homarr should start itself.
Same startup script as you use in docker image.
Okay, can you explain what you meant? I think I misunderstood. Why does a reboot help?
Like I said, I've tried using ip:port and domain+reverse proxy and I have the same websocket message. It seems the status change to "finished" but not 200 OK after 4 minutes and then there's another websocket entry marked as pending and this keeps happening when I leave the page be without doing anything.
Thank you for looking into this 🙂
Startup script tries to start a new redis session which may not got temrinated.
Rebooting ensures redis is also cleanly shutdown
Are you using port 300?
I can't really reproduce this :/
You want me to reboot the LXC? I can definitely do that but the LXC has been rebooted, shutdown, many times since I've setup this homarr instance. Will do it now.
*port 7575
It's using port 3000 and I've not added anything to that LXC.
Try with port 7575
If I try with same IP:7575 (http)I have a blank page. Am I supposed to first change a config file for the port 7575 to be considered?
Scratch that, Ive tried in another browser and I have the dashboard. I've came back to the original browser cleared cache and I have the dashboard. Will test now the WS and see how the integration behave.
I have websocket status 101
Solution
Yeah as it says on the website and after creating an lxc it is on port 7575
Wow! I'm so sorry. I must have overlooked this and used the same port my previous homarr install was using as habit.
This seems to work fine with port 7575. Out of curiosity, how come there's still something served at port 3000? Coming from the "old" homarr I went with 3000 and since I was able to setup everything using this port I've never questioned its legitimacy...
that quite simple, homarr does not have websockets itself, it uses an nginx instance, it basically "needs" an inbuilt reverse proxy, so we ship a basic nginx which is configured on port 7575.
For refercen for the homarr team @Manicraft1001, this is clearly mentioned on website and during install:
Yes you're right. I'm very sorry to have mobilized you on this. Clearly an overlook on my part..
Thank you all for helping me resolve my own mistake.
Oh that makes sense 😄
Yeah we use an nginx reverse proxy on port 7575 to serve the websocket server at
/websockets and the normal app at every other path. So if you just use 3000 it won't be able to connect to the websocket server 😉