Hardware: VPS bought online YunoHost version: 11.2.5 I have access to my server : Through SSH | through the webadmin Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no
Description of my issue
I am attempting to use the Redirect app to access a docker container running Corteza. The redirect app is set to 127.0.0.1:19080, the domain is a subdomain and the container is healthy. I can access the container via the user portal but it shows “Internal Error” instead of its auth page. A local instance (without Yunohost) works fine.
When I look in the Nginx service logs, I receive the following error:
2023/11/24 14:03:03 [error] 32556#32556: *530 open() "/usr/share/nginx/html/ynh_portal.js" failed (2: No such file or directory), client: 104.164.173.122, server: corteza.pncholdingsllc.com, request: "GET /ynh_portal.js HTTP/1.1", host: "corteza.pncholdingsllc.com"
2023/11/24 14:03:03 [error] 32556#32556: *531 open() "/usr/share/nginx/html/ynhtheme/custom_portal.js" failed (2: No such file or directory), client: 104.164.173.122, server: corteza.pncholdingsllc.com, request: "GET /ynhtheme/custom_portal.js HTTP/1.1", host: "corteza.pncholdingsllc.com"
Something in Nginx is pointing to nonexistent js files. The only file in /usr/share/nginx/html is the Nginx success page. Would appreciate any help you might offer!
The actual issue is probably not related to these error messages, “Internal error” usually corresponds to error 500, which happens in the app itself. You probably want to check the logs of the app itself.
After fastly reading the deployment docs, I think you might need to make some changes to the nginx config file (reload nginx after every change). Also, it seems that it needs its own domain, not a path. Another thing, the browser console can help understand what’s wrong.
And forget about these files, I also see the same error in my nginx logs from time to time and I don’t have docker installed.
Good luck
SOLVED: When I stood up my YNH server on a Hostinger VPS, the Diagnosis tool told me the DNS was working but it would be better if… So I changed the primary resolver (in Hostinger settings) to 127.0.0.1 and happily plowed ahead. YNH worked fine, no more DNS complainer.
In troubleshooting this issue with Corteza, I finally lost track of all the mods I had made to the server and decided to blow it up and start over. I wiped the server, reinstalled YNH, and ignored the DNS complainer. Corteza came up on the first run…
So either I’ve ignored a valid DNS issue that will bite me at some point in the future, or the complainer in Diagnosis is having challenges dealing with Hostinger VPS and how it handles DNS.
I appreciate everyone’s help. This one was a real challenge…