Open wandored opened 3 months ago
I pushed my current devel code which was working but still getting the 502 error on the production server. maybe it is something with nginx. I searched for logs but couldn't find any hints on what it is. See if you can find anything.
chatgpt:
The output from ss -tuln | grep 5000 shows that your application is indeed listening on port 5000 for TCP connections on all IPv4 addresses (0.0.0.0:5000). However, in your Nginx logs, the error indicates that it's trying to connect to http://[::1]:5000/, which is an IPv6 address.
Potential Issues and Solutions: Mismatch between IPv4 and IPv6:
Your application is listening on IPv4 (0.0.0.0), but Nginx is attempting to connect via IPv6 ([::1]). Since the application is not listening on an IPv6 address, the connection fails. Solution: Update the Nginx configuration to use the IPv4 address instead of IPv6.
its not nginx, its the response time from the application.
actually, there is a problem with the sales_detail table. all the times are 00:00:00. we must be doing this in the ubiquity_train script. It only affects the potato sales. I will work on a script for the potatoes only which preserves the times.
does this statement zero out the time?
df["date"] = pd.to_datetime(df["date"]).dt.date
edit: i removed '.dt.date' from the statements. That should hopefully restore the times.
Stores getting 502-bad gateway. Its working on test dashboard.