I have a server on a VM, it’s running perfectly but I want to access it from the internet. We have a reverse proxy in the company, but I can’t communicate with my server from outside the intranet. Is there an extra modification that I have to do to the config file? All ideas would be very appreciated.
The first question is which one? Apache, nginx … I have nginx running which proxies the data to uwsgi which runs Tryton. Keep in mind that Tryton have to run on the root, so you maybe have to create a separate subdomain.
So generally speaking, you have a WSGI server which runs Tryton (NEVER use the development server in production!). If the WSGI server is working, you can connect the reverse proxy to it through a socket or port. You have to do configuration on the WSGI server and the reverse proxy server.
It can also be a firewall problem in the way that the proxy server is not exposed to the internet.
Search this forum with 'reverse proxy` and you get several topics about it.
I run an Apache2 reverse proxy with no problem (ip4)
If your proxy cares about certificates, it can forward traffic to Tryton port.
Logging on the proxy, can you reach your VM ?
I would check if ipaddress is pingable and if iptables are correctly set in case you use NAT.
Setting up a production server can be a bit tricky, especially when you’re trying to access it from the internet. I was in a similar boat a while back. I had my server running smoothly on a VM, but the reverse proxy made things a bit complicated. One thing that helped me was considering 4G/LTE/5G rotating mobile proxies. They can provide a dynamic IP, which might make it easier to communicate with your server externally without getting blocked. I found that using a mobile proxy really improved my access issues. Just a thought! I’m excited to learn from everyone and share experiences.