Front end is blank #72
Comments
|
The DNS is a requirement and is only there to force the feeder to connect to feedernet instead of the petnet servers that no longer exist. As far as the blank page, I would double check your nginx config. You should also be able to connect to the feedernet service directly at your raspberry pi's IP port 5000 (per your screenshots, http://192.168.1.21:5000). That would bypass nginx so you can see if that's the problem. I just setup mine yesterday so maybe I'm missing something here but that's what I noticed with my experience with this so far. Just trying to help :) Edit: I noticed in the logs that it's requesting some of the files for the UI so maybe it's just an error in the react app. In my experience with react, the white screen can also mean the react app crashed. In that case, you might also see some info in the browser console (press F12). |
|
@johndc7 Thank you! Including the port helped and I am able to see the front end. Not sure why it's not working otherwise or if that signals any problems I should be concerned about. I cannot use https either and I am not sure what part of the setup contains the HTTPS proxy. |
|
The https certs are generated by the feedernet service and used by nginx. If it loads from port 5000 then it sounds like the feedernet service is working. You can also see that the certs have been generated properly in the log file you attached: I would check:
|
|
Merp. I have no idea why it's not working. My nginx config file and docker-compose yaml files look fine. The cert files are there. I'm assuming this has to do with my lack of knowledge of how DNS works. I think I need a SRV record to point it to the right port? My A records are redirecting to my raspberry Pi just fine so I don't know what else it could be. To clarify, My feeder will not connect to my server. I can get to my server just fine using the IP address and port or FQDN like this: http://api.arrowconnect.io:5000/ but I have to include the port number and use HTTP. If I don't include the port number or I use HTTPS, I get hella errors like 504 errors, connection closed, that blank page or any combination of that with "site isn't secured" messages. I think what I would like to know is if certificate errors are normal or if when this project is working properly, I should be able to use HTTPS without any errors at all. Because it would make a lot of sense if the feeder won't connect unless SSL is present. |
When you set this up, there are 2 different containers running in docker. One of them is the actual feedernet service (bound to port 5000) and the other is nginx (bound to port 80 and 443). All nginx is doing is forwarding the traffic to the feedernet service on port 5000. The If you can access the feedernet service on port 5000 but not over https (443) it sounds like it would be an issue with the nginx container. The site isn't secured messages are normal since it's a self-signed cert (you don't own the domain arrowconnect.io so it's not possible for you to get a legit one). This doesn't really matter since the petnet feeder doesn't actually check if the cert is valid. It only requires that one is there since the petnet servers were over https. You should be able to continue to the site anyways. |
|
@johndc7 Okay thank you. This info is very helpful. Honestly I think I might just re-image my raspberry pi and start the project from scratch. Thanks for your help! |
|
It would be helpful to see the developers console output from your browser. I have fixed quite a bit of problems from the Bootstrap 5 upgrade since your original report. |
Awesome I will give it a shot thank you. |
|
Hi I installed everything on a fresh raspberry pi image. Can't get frontend up at all now and getting hella errors in the docker logs: petnet-feeder-service | Traceback (most recent call last): |
Hello! Thank you for creating this project as it will be extremely helpful once I get it up and running.
I have read over the Wiki extensively and followed the all the steps except for creating my own DNS server.
I do not plan on using the mobile app and really only need to configure the feeder in a "set and forget" manner.
I do not mind accessing it just by IP address.
I only ran into a couple of snags during installation which were resolved by updating the docker packages with apt upgrade and adding my user to the docker group. All of the terminal commands listed in the Wiki run successfully now.
The issue now is when I attempt to navigate to the front end, I am met with a blank page.
You can see from my RaspberryPi here:
After fiddling around with the URL, thinking I had missed something obvious like /home or /feeder I was met with a 504 error when trying to access it from my computer (instead of my RPI). This error persists even after a reboot of the RPI.
Is it completely necessary to setup a DNS server for this project to function? Or is that for mere ease-of-access to make the mobile app work and make a vanity URL for a computer?
I have also attached my logs from docker in case that is useful.
I hope I haven't missed anything obvious or misunderstood the instructions. If I have please let me know, I am happy to learn.
Any help is appreciated. Thank you so much.
logs.txt
The text was updated successfully, but these errors were encountered: