Everything feels so slow and buggy?

[Bajiio]

Hello everyone,
I just installed homarr on my self hosted server after seeing incredible demo from youtube. I'm kind of confused right now, because everything seem so slow. For example, after putting credentials, the dashboard take almost 10sec to appear (and the weather integration 10sec more), the app config works fine, but once again if I want to go into dashboard setting and come back using the "back to board" button, it just never works, taking more than a minute to comeback on dashboard. I have no clue about what could be the cause, and pretty confident that my server has more than enough resource than needed for it. Is there something I could check to have data / logs about that kind of problem ? Does anyone already had this kind of problem ?

[S7YX]

Hello Bajiio
I installed Homarr today and also noticed the slowness.
I have not commented out the following line under Portainer in the stack to see the full range of functions :
- /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration
After I re-rolled the stack without .sock, the performance was much better.
Give it a try, you may see the same results.
Best regards

[S7YX]

Hello again

I have Homarr running via Portainer on a Synology.
In the Synology firewall rules I have only allowed port 7575 for Homarr, but this does not seem to be all, because the weather widget does not show any data until I disable the firewall on the Synology.
Could this also have an impact on performance when connecting to Docker via Sock?
I haven't tested it yet, just as food for thought.

Best regards

[S7YX]

I have now found some time to continue exploring Homarr, Synology and Docker.
Homarr now runs more smoothly for me, even with Docker integration.
I also had a problem with Homarr in that the weather widget did not show any data and the dialog for creating new apps did not return any results in the Appearance - App Icon section.
I then created a firewall rule on the Synology Diskstation that allows ports 5_3 tcp/udp , 80 tcp and 443 tcp_ with the source IP from the container.
This gave me a working widget and the icon search also worked, as well as better performance from Homarr.
Whether the performance of Homarr really depended on this is beyond my modest knowledge.
Since I also lack the knowledge of how a container always gets the same IP with Docker when it is rolled out again (update), I changed the firewall rule on the Synology to source IP range 172.16.0.0/255.240.0.0 .
But this also solved my Mailrise problem and Mailrise is now successfully sending messages to Telegram.

Best regards and good luck!

[manuel-rw]

There is currently a bug that affects the loading time of Homarr significantly when you have the docker integration enabled. It will be fixed in the next version.

Additionally, we are making improvements to the performance with an upcoming rewrite of the drag and drop system which is responsible for most lag.