Hi.
The next explorer app stucks at deploying stage even with a minimal configuration.
So, whats the deal with it?
So anyone using nextexplorer app? I could not get it to work, it is stuck at deploying stage.
Hmm… does anybody successfully deployed this app? Really like to get it working and trying out, but it is stucks at deploying stage forever. Am I doing something wrong? The logs only says changing uid:gid from 999:999 to 568:568.
Yeah just tried and get the same result… you should propably file a bug report at
Filed a bug report.
So my bug report is closed. With the comment, looks like my apps pool is on HDD, thats why it takes 10-15 minutes to chown the files!
But hey, my apps pool is on an nvme SSD! 
So guys… that was not very helpful.
Now I am installing it again and will wait when will it be “running”.
And yes, it is running now.
It took 25 minutes to chown the files on an SSD pool!
2025-12-05 15:45:31.765974+00:00INFO: Updating appuser UID:GID from 999:999 to 568:568
2025-12-05 16:10:03.098079+00:00INFO: Launching process as appuser (568:568)
Just WTF, did not expect that, especially when you not mount any additional storage to it (at least I did not in my test)
Yeah, I tried it either way… Now I am trying with 999:999 but it seems like it will take the same time to deploy. It is strange because this time it do not need to chown anything and it is not wrote anything to the logs yet.
It is nothing to do on an additional storage. If I understand correctly, it is chown the container files at startup. If you have not add any browse-able storage to the container, it is take that much time too!
Hi, author of NextExplorer here. I noticed this issue that I was trying to chown /app, this issue has been fixed now in the latest releases.
Hi Vikram_Soni!
Thank you a lot. Now it is working like charm! I am now testing it and I think I will be using it for my photos and videos collection. I like it very much.