Insane slowness + how to setup systemd
Its almost impossible to do anything on homarr as I see the webpage trying to load something perpetually, and it only respond to my clicks once I tell my browser to stop loading, then I can click and as soon as I click anything in homarr the webpage goes into infinite loading again and I can't interact with anything yet again.
I see that whenever I try to interact with stuff and nothing works because of the infinite loading, I see that no new entries shows up in the console, only when I do my "trick" and the website responds again is when I see new entries. Sorry for explaining it poorly.
I had a guess that it might be because it is running on the console by pnpm start and maybe if I create a service it would be better, however I have no idea how homarr actually runs so I can't properly create a systemd service and gpt couldn't either because it is looking for "apps/nextjs/.next/standalone/server.js" to create the service.
I would appreciate any help.
Build from source. Ubuntu 24.04.2 LTS. Node v22.14.0. pnpm 10.8.1. Redis server v=7.4.1
42 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?
Hi, thanks for the post. Don't worry, the explanation was good enough to understand.
When running from source, it is important to follow our guides closely, build the application and run the production server.
You'll also have to deal with breaking changes, updates, dependencies and more. Therefore we usually never recommend users to run from source, unless they know what they're doing and have enough programming knowledge.
Is there a particular reason, why you want to run from source? Have you considered our other installation methods, such as Docker?
I don't work with dockers, I'm running VMware and not proxmox or unraid
out of all the options the only one that gets close to good ol vms is building straight from source
believe me its not my favorite way either, but thats the only option that fits the bill
Everything was build without errors, its the only reason why I'm here
Ok, no worries. Usually, many users just run from source by default, without understanding why and how to do so - hence I'm always asking what their use case is. But if you just want to run using VMs, you're right 👍
Can you post your build errors here?
There were no errors during build
Ah sorry, misread without to with 😄
You followed these steps? https://homarr.dev/docs/next/getting-started/installation/source#steps
Do you use external
mysql2 or better-sqlite within the VM?
How is your VMware VM provisioned?Correct I follow those steps to a T.
SQLite version 3.45.1
provisioned as in the disk drive? No sure exactly what information you are looking for
4 Cores, 32GB of RAM, 30GB Thin provisioned on a ssd
Does that help?
Yes, but how much does the Homarr VM have? It should have enough CPU & RAM, otherwise that'd explain the slow responses
oh, thats whats is assigned to it
the host has way more
didn't think a dashboard would need more
Ah, ok that is waaay more than required. So hardware definetly isn't an issue then
No, you could downscale to 2 vCores and 4 GB Ram actually. But I wonder why your instance is so slow then
Can you post your logs?
!qa required_data
Thank you for your question. Our support team has noted that your request does not meet the minimum required data so we are unable to answer your question.
Please provide:
- your Homarr logs
- your setup configuration (eg. docker compose, docker run, helm chart, screenshot, ...)
- A detailed description of your problem or question with additional images where necessary
- Your operating system
- Version of Homarr (do not say latest! say 0.15.2, ...)
Failure to comply with this will result in a permanent closure of your support request.
I was going to send the log... however the guide on your website doesn't point me where it would be in my case
I didn't see any obvious log files, sorry
We never log to a file, so it must be in stdout
And depending on how you setup that in your VM, it will be completly different. I can't help you with that
forgive me but I'm a little unfamiliar with the term stdout, are you refering to everything that gets printed to the screen when I run homarr?
with pnpm start?
https://linux.die.net/man/3/stdout
Yes, stdout is the output of that
quickly running homarr to get you some logs. Decided to interact with the site for a second and take a screenshot in the hopes of better explaining my issue (I still think I did a poor job of doing so).
As you can see from the Firefox tab, the site loads indefinitely, you can also see that the refresh button is showing as X. And the new board window that I have currently open in homarr is frozen and I cannot click create. (This is an example of homarr being frozen and not specific to new board creation)
Follow the stdout:
@Meierschlumpf almost looks like tRPC was being compiled but when looking at the logs, it looks like a production build.
I don't see anything out of the usual things, do you have an idea?
@Meewbs please wait for Meier to reply. Thank you!
:VanillaPray:
⚠ "next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead.
I think this is the problemI'm sorry Meier but I don't think I quite understand
I almost assumed for a second that I should start homarr by using server.js however my project folder does not seem to have a .next folder
When running
pnpm build it should create one in apps/next/.nextyou mean nextjs?
Yes sorry
I do not have server.js inside the standalone folder
Have you ran
pnpm build before? It should get created by itI did but I can run again, one minute please
It's possible that it's under apps/nextjs/.next/standalone/apps/nextjs/standalone.js
found server.js in there
I unfortunately seem to be getting spammed with invalid env variables
Have you defined the
SECRET_ENCRYPTION_KEY?
!qa leaked_secret_key
Our team noted that at least one of your messages contains a secrets encryption key used in Homarr.
As documented at the installation docs, the secrets encryption key is a cruicial key that will be used to encrypt your data. By posting this key you compromised part of your security and we strongly recommend you to change it, since malicious acters could gain access to your integration passwords, usernames and tokens by decrypting your database if they gain access to said database.
To do this, update the secrets encryption key variable. Doing so will break all integrations and you must manually re-enter the secrets again.
Manually removing it after posting does not fix your issue since automated bots can and will scrape messages for leaked data.
To avoid such problems in the future, please always remove the encryption key when posting online. The Homarr team will never ask you for any passwords or the secrets encryption key.
Docker | Homarr documentation
Docker is our recommended installation method for beginners and professionals.
I do understand the concern about the key
it will be changed later when the issue is fixed
thank you
Did you just run
node server.js?
Or did you specifiy something to load the .envforgive I did not, I'm not familiar with node. Could you assist me?
because in the package.json of nextjs package we have
pnpm with-env next start
So it might work with pnpm with-env node ./path/to/server.js, but I think in general it would make most sense if we would change the start command of nextjs to run the nodejs server.js filemissing images, and the issue persists of not being able to click anything