how to hide Server Version of Phusion Passenger(R) 6.0.10 - nginx

I want to delete the "Phusion Passenger(R) 6.0.10" so it won't show in headers
How can I do it, please
thank you
X-Powered-By Phusion Passenger(R) 6.0.10, cloud66

Related

How do you change the server header returned by nginx?

I am using Nginx v1.23.3.
I was trying to hide the server header returned by Nginx. But I don't see any option to hide the server header for Nginx v1.23.3.
If I try to install Nginx-extras my Nginx version is downgraded to 1.18. So is there any solution to hide/remove the server header in the response?

Access-Control-Allow-Origin' header contains multiple values 'http://localhost:4200, *', but only one is allowed

I use angular on the front end and .net5 on te backend. I deploy my backend to ubuntu 20.04 server and run it with nginx.
I faced this issue while attempt to login. My get functions works well but login(post) is not.
I searched hours and hours and add add_header Access-Control-Allow-Origin *; to my etc/nginx/sites-available/default file.
But nothing changes. Do you have any idea?
Does your .NET backend allows CORS
e.g
have a look at https://learn.microsoft.com/en-us/aspnet/core/security/cors?view=aspnetcore-6.0
Also while you are modifying NGINX conf make sure to restart the service.
e.g
sudo systemctl restart nginx

How to install Nginx on OpenShift

Though I followed https://blog.openshift.com/lightweight-http-serving-using-nginx-on-openshift/ step by step, I ended up getting the error 503, telling me service is unavailable. There are questions on various websites, including stackoverflow, but all of them are about issues after a successful installation of nginx, a point I haven't arrived at yet.
I don't want to use already available cartridges - in part because most of them are out-of-date. Also, an answer to my question might be of interest to some people, inasmuch as it will teach how to run always the latest nginx server on OpenShift.
This is rhc tail result
DL is deprecated, please use Fiddle
==> app-root/logs/diy.log <==
[2014-12-06 16:55:47] INFO WEBrick::HTTPServer#start done.
[2014-12-06 16:55:50] INFO WEBrick 1.3.1
[2014-12-06 16:55:50] INFO ruby 1.8.7 (2013-06-27) [x86_64-linux]
[2014-12-06 16:55:50] INFO WEBrick::HTTPServer#start: pid=255959 port=8080
127.xx.x.xxx - - [06/Dec/2014:17:11:57 EST] "HEAD / HTTP/1.1" 200 0
- -> /
127.xx.x.xxx - - [06/Dec/2014:17:11:57 EST] "HEAD / HTTP/1.1" 200 0
- -> /
[2014-12-06 17:32:02] INFO going to shutdown ...
[2014-12-06 17:32:02] INFO WEBrick::HTTPServer#start done.
==> app-root/logs/server.log <==
nginx: [emerg] invalid port in ":" of the "listen" directive in /var/lib/openshi
ft/xxx/app-root/data//conf/nginx.conf:36
This guide (2012 year) uses environment variables: $OPENSHIFT_INTERNAL_IP:$OPENSHIFT_INTERNAL_PORT
Now it was renamed to:
$OPENSHIFT_DIY_IP:$OPENSHIFT_DIY_PORT
If all you want is nginx on OpenShift I would use this cartridge instead
https://github.com/gsterjov/openshift-nginx-cartridge
Here's a cartridge that's updated to the most recent nginx 1.9.12

nginx shutting down because of fastcgi_keep_conn

I am having a weird problem with nginx configuration.
The server doesn't boot if I don't comment this line in nginx.conf
#fastcgi_keep_conn on;
And it is uncommented everytime(overwritten) nginx crashes or if the system reboots
I am not sure if I am missing that module or if I have to install additional packages. Could someone point out the error?
Error in /var/log.nginx/nginx.log
unknown directive "fastcgi_keep_conn" in /etc/nginx/nginx.conf:29
The fastcgi_keep_conn directive appeared in nginx version 1.1.4 (released 20 Sep 2011). So your nginx version is too old, and doesn't support keepalive connections, as well cannot know about the directive.
Please, also note that your nginx is obsolete and not supported. You should update it ASAP.

Why does Passenger 3.0 with nginx crash on startup(?) then 403s?

On Ubuntu with REE 1.8.7, with nginx 0.8.53 manually compiled with the
Passenger 3 module doc installed as per the docs, I get an error in
the nginx error log when nginx starts:
Unable to start the Phusion Passenger watchdog because it encountered
the following error during startup: Unable to start the Phusion
Passenger logging agent: an error occurred while sending startup
arguments: Broken pipe (32) (-1: Unknown error 18446744073709551615)
I assume this means nginx never starts properly. When I try and view
my site after this, I get a 403.
2010/10/22 00:56:47 [error] 13874#0: *1813942 directory index of "/var/
rails/myapp/current/public/" is forbidden, client: 125.197.115.16,
server: new.myapp.fm, request: "GET / HTTP/1.1", host: "new.myapp.fm"
I expect the first is probably causing the second. I haven't had any
luck googling this. Can anyone provide insight or help me
troubleshoot?
I got this after upgrading to Passenger 3.0.1 as I had not changed the version of Passenger specified by passenger_root in /opt/nginx/conf/nginx.conf. You might need to change the line that looks like this to specify the correct version:
passenger_root /usr/lib/ruby/gems/1.8/gems/passenger-3.0.1;
You get told to do this when you install nginx. Hope that helps.
I ran into this problem too, and it was because passenger couldn't find ruby:
tail -f /var/log/nginx/error.log
2011/12/20 00:54:45 [alert] 30300#0: Unable to start the Phusion Passenger watchdog because it encountered the following error during startup: Unable to start the Phusion Passenger helper agent: it seems to have crashed during startup for an unknown reason, with exit code 1 (-1: Unknown error)
* Passenger ERROR (ext/common/ApplicationPool/../SpawnManager.h:220):
Could not start the spawn server: ruby: No such file or directory (2)
Even though ruby was properly listed within the system PATH, it didn't seem to work right until I added:
passenger_ruby = /usr/local/bin/ruby;
(the location of my ruby executable) into the http section of my nginx config.
The problem was that PassengerLoggingAgent wasn't installed when I did 'gem install passenger'. I installed it as per this discussion (by grabbing it from the standalone zip) and everything is fine now: http://groups.google.com/group/phusion-passenger/browse_thread/thread/323dc1c7b0e5ee11

Resources