Traccar SMS Gateway with Nginx
There must be some issue with your proxy configuration. Jetty should work just fine behind proxy.
Hello Anton, first of all thank you for your work and your answer here in the forum. Of course, you can be absolutely right. On the other hand, I have 20 applications that I have integrated via the Nginx, with which I have no problems at all. On the other hand, they do not use any specially adapted headers for authentication.
In my search for a cause, I came across two topics:
1.) https://support.datameer.com/hc/en-us/articles/217011326-How-Do-I-Configure-NGINX-as-a-Proxy-to-Jetty-
Here someone writes that something has to be embedded in Jetty first. However, I am not familiar with Jetty.
2.) https://www.itsupportwale.com/blog/fixed-nginx-showing-blank-php-pages-with-fastcgi-or-php-fpm/
Here, the display of a blank page in connection with fastcgi is being traced. There are many other pages if you search for "blank page nginx".
However, this is always described in the context of PHP.
Does the Jetty use fastcgi in any form?
This seems to be related to proxy headers. I think its optional. It just lets server know original request details.
Jetty doesn't use fastcgi.
It doesn't matter if you are connecting through a proxy or directly. Server doesn't really distinguish between the two. There's no difference. Therefore there's no additional configuration required on Jetty side.
Okay, I have now found the error. That was my mistake. Port 80 was forwarded directly to the web server (Apache) - without passing through the ReverseProxy. The index.html is an empty page here.
So I can confirm here that the SMS gateway works problem-free with Nginx.
@Azathoth88
Can you show how you have done this setup..
If you want to implement my "setting"... look here: https://www.linuxserver.io/blog/2020-08-26-setting-up-authelia
But that will probably be too much for you. However, there are sufficient instructions on the internet on how to install an Nginx as a reverse proxy.
Hello, I have been trying to integrate the SMS gateway via a Nginx (SWAG) for over an hour. Unfortunately I do not want to succeed.
The gateway works in principle. I can call it externally via PHP with domain.tld:8082 and send SMS.
However, I would like to do without the additional port and call the gateway via subdomain.domain.tld.
Ideally, protect the connection with HTTPS.
All attempts so far have led to a white page.
It almost seems to me that the Jetty(?) server does not support proxy requests.
Has anyone been able to get this to work?