[RoninUI] 502 Bad Gateway / Could not find a production build in the '.next' directory #9
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
After building RoninOS and running the plug'n'play setup on a new machine, I noticed that the webpage of RoninUI does not work any more. I was greeted by "502 Bad Gateway". Oooff. Nginx seems to run, but there is nothing behind it to serve.
In
roninui.log, I see thousands of errors, always the same one:I also noticed an odd-looking and empty directory named
nextjs-nodejsin /home/ronin/.config/. What is this?There is a
.nextdirectory created in "/home/ronin/.ronindojo/roninui/", even with contents in it, but how can we be sure it is complete and accessed by the webserver?However,
setup.loglooks fine, no error there — "All RoninDojo feature installations complete!"What went wrong here, can someone have a look? Some of the latest changes must have produced this.
... also, if it is not asked too much, it would be very helpful to configure the Gitea server in a way, that attachments and pictures are processed and served correctly. There is
localhost:3000in the links everywhere, instead of the .onion domain. I already noticed this earlier during the registration process and the emails coming from Gitea. Maybe someone can get hands-on with it and have a look at the config again. As you probably can see above, it's very crippling.I investigated further: the errors are already happening when building the RoninOS image. So nothing is there for the plug'n'play setup to serve later.
There are dozens of errors; see full error list in the attached textfile.
It seems, this is happening when calling the function
_install_nodejs_and_ronin_ui. Maybe a path set wrong?My guess is, it's in here:
Big change incoming here: PR#10. Maybe this issue was addressed or evaporated. Everyone should test thoroughly with #10.
It evaporated.
After entertaining myself for several days and a complete remake of my whole build environment, it now works again. As usual.
This is where joining the matrix will be helpful. Coordination and comparing build enviros can happen at a much faster pace.