Francis Daly wrote on 9/4/2023 1:05 AM:
proxy_passhttp://127.0.0.1:5443;
You probably have a space after proxy_pass in your actual config; but
you probably should also have "https://"; not "http://"; there as well,
since your upstream service is listening for https connections
On Sun, Sep 03, 2023 at 09:57:54PM -0700, Sam Hobbs wrote:
Hi there,
> curl -k https://127.0.0.1:5443
>
> (the address that Kestrel is listening to) I get a page that I am expecting.
> proxy_passhttp://127.0.0.1:5443;
You probably have a space after proxy_pass in your actual co
has accepted the certificate.
When I browse to the domain from another system (over the internet)
Cloudflare is saying 502 Bad Gateway and that the problem is in the
server. Is there a log somewhere showing the incoming request and more
details of the error?
The following is my server block
´t find a contact adress.
Greetings
Hans
Gesendet: Freitag, 03. März 2023 um 21:45 Uhr
Von: "Maxim Dounin"
An: nginx@nginx.org
Betreff: Re: Reverse Proxy 502 Bad Gateway
Hello!
On Fri, Mar 03, 2023 at 04:33:25PM +0100, Hans Müller wrote:
> Hello,
> I am working in a pro
ellinabox is
>installed. Request from the internet are secured via a Letsentcrypt
>certificate. For the encryption to the backend server I use a
>self-signed certificate.
>When I want to open the next-shell.example.com I get an 502 Bad Gateway
>error
>
encryption to the backend server I use a self-signed certificate.
When I want to open the next-shell.example.com I get an 502 Bad Gateway error
On the reverse proxy are the following configs
HttpGateway
server {
listen 80 default_server;
listen [::]:80 default_server;
server_name
Francis Day,
Wow ... that did it! You resolved my issue! After troubleshooting for 1 full
week of troubleshooting, it's resolved! Thank you so much!
So I edited my /etc/nginx/sites-available/discourse.conf file:
* I changed THIS line:
proxy_pass http://discourse.domainame.com:8080/;
To THIS lin
On Sun, Nov 17, 2019 at 06:40:36AM -0500, naupe wrote:
Hi there,
> > root@ngx:/etc/nginx/sites-available# less /var/log/nginx/error.log
> > 2019/11/17 06:01:24 [error] 23646#23646: *37 connect() failed (111:
> Connection refused) while connecting to upstream, client: 1.2.3.4, server:
> discourse.
the same Private IPs to the same MAC Addresses, and
opening the same ports for the same Private IPs). However, with my Discourse
VM, I am receiving 502 Bad Gateway - nginx/1.14.0 (Ubuntu) when trying to
access Discourse in a Browser.
In the past, it was usually through the Discourse software that I
Hi,
Does nc -l 9000 gives the same bind error ?
If so, better to check netstat for :9000 sockets with all status, like
netstat -anp | grep :9000
to get an idea.
Regards,
Lahiru Prasad.
On Mon, Oct 7, 2019 at 11:38 AM mmpl wrote:
> Error 502 Bad Gateway on nginx and php-fpm
> Pos
Error 502 Bad Gateway on nginx and php-fpm
Posted by: mmpl
I can't start php7-fpm in supervisor. The error log:
unable to bind listening socket for address '127.0.0.1:9000': Address in >
use (98)
In browser:
localhost:8090 is error: 502 Bad Gateway
netstat -tulnp
tcp 0 0 0.
Ken,
proxy_buffer_size and proxy_buffers are very similar.
These configure buffers allocated for a response from an upstream.
Both are documented here:
http://nginx.org/en/docs/http/ngx_http_proxy_module.html . Please, have
a look.
The difference is that proxy_buffer_size buffer is always all
On 8/14/19 3:37 AM, Igor A. Ippolitov wrote:
> Ken,
>
> Try setting 'proxy_buffer_size' to a higher value. Say 128k.
Umm, what file would I find that in? I've seen so many similar
statements lately I can't keep them straight. Sorry for being so dumb!
Ken
--
Registered Linux user #483005
I
> understand what's going on; nginx says it's working, and php shows the
phpinfo page
Thanks for that. Reading your comment about the phpinfo page made me
repoint my root to the default html directory root web directory to test for
the phpinfo page and I do not get it. I checked my sights-avai
Ken,
Try setting 'proxy_buffer_size' to a higher value. Say 128k.
On 14.08.2019 8:47, Ken Wright wrote:
Maxim and anyone else who cares to chime in,
I'm still enough of a newbie that I have trouble understanding the error
logs. The one for nginx reads the following at the end:
2019/08/12 22:
Maxim and anyone else who cares to chime in,
I'm still enough of a newbie that I have trouble understanding the error
logs. The one for nginx reads the following at the end:
2019/08/12 22:48:51 [error] 8274#8274: *1 upstream sent too big header
while reading response header from upstream, client
I am also having this problem on my Linux box I run at home. I had the
webserver running perfectly then followed directions to activate virtual
hosting. That also started out working perfectly for a while then suddenly
I was getting the 502 error when launching anything from the static site. I
r
Hello!
On Mon, Aug 12, 2019 at 11:35:12PM -0400, Ken Wright wrote:
> I'm running nginx 1.14.0 on Ubuntu Server 18.04 with PHP 7.2.19 and as
> of this morning I'm getting 502 errors when I try to log into Nextcloud
> (16.0.3, if it matters). I know I've seen fixes for 502 before, but
> nothing I'
I'm running nginx 1.14.0 on Ubuntu Server 18.04 with PHP 7.2.19 and as
of this morning I'm getting 502 errors when I try to log into Nextcloud
(16.0.3, if it matters). I know I've seen fixes for 502 before, but
nothing I've been able to find thus far has helped. Further information
available on r
Hello,
I'm sucessfully accessing a server/site behind my reverse proxy with the
following URL
https://app.mydomain.org/screens/dashboard.html#/MainDashboard
But the following URL gives a 502 Bad Gateway
https://app.mydomain.org/screens/webui/resource/swccopolldata.json
I don't unde
Hi Reinis Rozitis, yes it seems to be a plugin.. I am in contact with the
developer to see how to fix it..
Thans for your interest and reply
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,270759,270857#msg-270857
___
nginx mailing list
nginx
> If you do not need nginx anymore why you do not uninstall it?
I don't think the OP is running nginx (at least Server headers say it's apache).
It looks like though that the error could be coming from an external resource.
While inspecting the html source it seems generated by php (rather tha
ys I am getting this error message all over my website:
> 502 Bad Gateway nginx/1.2.1
>
> The thing is that my server uses apache... I have tried solutions I have
> found in google: erasing cache files on navigator and pc. and doesn't work.
> I have talked to my server administra
Hello,
since a couple of days I am getting this error message all over my website:
502 Bad Gateway nginx/1.2.1
The thing is that my server uses apache... I have tried solutions I have
found in google: erasing cache files on navigator and pc. and doesn't work.
I have talked to my s
I've played with proxy timeout settings, no luck. And nothing was logged on
the backend-server.
Finally I've found something in the firewall log:
May 27 10:25:06 APZRP01 kernel: DROP: IN=APZRP01 OUT=
MAC=c4:34:6b:af:19:64:e8:65:49:28:08:77:08:00 SRC=10.59.55.245
DST=192.168.57.14 LEN=40 TOS=0x00
Check the logs of the apache server.
You might need to tweak the proxy_*_timeout settings in nginx , but
usually its the problem with the upstream server that is causing this.
try connecting to the upstream via http://domain:port directly and you
should face the error.
On Tue, Sep 13, 2016 at 3
I don't think there is an OS relation on the frontend, the same problem
occurs with an Centos Nginx as Reverse proxy in front of 3 Apache backends
on Centos - but it never occurs on windows based Apache backends...
But we´re on version 1.11.4.1 Lion (http://nginx-win.ecsds.eu)
Posted at Nginx For
hheiko Wrote:
---
> I've noticed the same problem between Nginx Proxy (Win) and CentOS
> based Apache 2.4 Backends. So I finally changed all backends to
> nginx+php-fpm...
What version of nginx are you running on Windows? (Asking because I am ju
I've noticed the same problem between Nginx Proxy (Win) and CentOS based
Apache 2.4 Backends. So I finally changed all backends to nginx+php-fpm...
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,268306,269500#msg-269500
___
nginx mailing lis
The problem still seems to persist. I am now trying to investigate this
myself. Any advise for debugging?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,268306,269498#msg-269498
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org
The error I am getting in the logs:
"upstream prematurely closed connection while reading response header from
upstream"
After the first request it works for 10-15 seconds without any problem.
According to tcpdump in the first request (the failing one) the upstream is
receiving one GET and nothi
setting up a nginx as a reverse proxy but to try to see a site
with drupal locally that have shown me 502 Bad Gateway error.
"drupal" is possibly served by a http server, not a fastcgi server.
> this gets me in the logs.
>
>
> 016/07/02 00:51:57 [error] 18120#0: *61 upstream s
On Sat, Jul 02, 2016 at 06:21:38AM +, yair avendaño wrote:
Hi there,
> Hi I'm setting up a nginx as a reverse proxy but to try to see a site with
> drupal locally that have shown me 502 Bad Gateway error.
"drupal" is possibly served by a http server, not a fastcgi se
ev/shm/php-cgi.sock',restart nginx and PHP,all done!
P.S:My mother tongue isn't English,if there is something you couldn't
understand,please let my konw,thanks!
2016-07-02 14:21 GMT+08:00 yair avendaño :
> Hi I'm setting up a nginx as a reverse proxy but to try to see a site with
Hi I'm setting up a nginx as a reverse proxy but to try to see a site with
drupal locally that have shown me 502 Bad Gateway error.
this gets me in the logs.
016/07/02 00:51:57 [error] 18120#0: *61 upstream sent unsupported FastCGI
protocol version: 72 while reading response header
Please help me too.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,238322,267020#msg-267020
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ot;
-- they are different errors, with different causes.
> Trying to access the site through curl gives me 502 Bad gateway
> error. I have also checked the Nginx error log which shows this -
"bad gateway" is a different error, with a different cause.
> connect() failed (11
Yes, I followed the instructions as-is and they work. The problems begin
when I block Tomcat from listening to external IPs by adding
address=127.0.0.1 in the Connector blocks. The Atlassian guide does not
discuss that aspect at all.
>From what I have observed, I feel that even if I have a Nginx
Hello,
did you followed the atlassian-guide?
>
https://confluence.atlassian.com/jirakb/integrating-jira-with-nginx-426115340.html
>
https://confluence.atlassian.com/confkb/how-to-use-nginx-to-proxy-requests-for-confluence-313459790.html
usually when nginxy says "502" you should trust this.
for
y 8080 and
8443 connectors, things stop working i.e., the JIRA site becomes
inaccessible. Browser displays Connection refused / connection timed out
errors. Trying to access the site through curl gives me 502 Bad gateway
error. I have also checked the Nginx error log which shows this -
connect() f
yes, agree.
Thanks Lucas.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,265576,265588#msg-265588
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
t installed:
- FreeBSD 10.2
- Nginx 1.8.1
- PHP 5.5.33
Nginx works fine with PHP that the web sites seems ok to run php pages.
However, once I run php on command line (e.g. php -v), the web site
will get
"502 Bad Gateway" error, and I find the nginx error log as below:
[error]
Eventually I find what went wrong, it should be caused by both Zend OPcache
and XCache are installed, they may conflict each other in this case, once
I've removed the XCache, it works fine, the php command line would no longer
cause the php-fpm error.
XCache should be unnecessary when OPcache is r
hi, on command line, when I type: php
or
php -v
after pressing [Enter] key, then the "502 Bad Gateway" will occur at once.
It is very strange, because I always think php command line should not
affect the php-fpm...
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,265576,
"502 Bad Gateway" error, and I find the nginx error log as below:
[error] 714#0: *3 upstream prematurely closed connection while reading
response header from
upstream, client: _, server: www..com, request: "GET / HTTP/1.1",
upstream: "fastcgi://unix:/
var/run/php
I have just installed:
- FreeBSD 10.2
- Nginx 1.8.1
- PHP 5.5.33
Nginx works fine with PHP that the web sites seems ok to run php pages.
However, once I run php on command line (e.g. php -v), the web site will get
"502 Bad Gateway" error, and I find the nginx error log as below:
[er
I've also seen the issue when running plain nginx 1.9.11 sort like builting
a new nginx, only the issue is that upstream closes cnxs, not nginx.
Since I've discovered that our TCs had the Connector' keepAliveTimeout way
low (10 msec), mistakenly thought the units were sec and not as actually
msec.
Hi.
Am 04-03-2016 11:00, schrieb stefws:
stefws Wrote:
---
Seems I'm not alone w/TC issues ;)
missed the link:
http://permalink.gmane.org/gmane.comp.web.haproxy/26860
Well Maybe you have a completely different situation.
Is it possible to b
stefws Wrote:
---
> Seems I'm not alone w/TC issues ;)
missed the link:
http://permalink.gmane.org/gmane.comp.web.haproxy/26860
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,265031,265079#msg-265079
_
Seems I'm not alone w/TC issues ;)
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,265031,265078#msg-265078
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
@B.R. You're right, seemed my upstream tomcat instances were RESETing cnx as
reply something.
So far I improved it a lot my altering a http connector keepAliveTimeout
value from mistakenly expressed as sec when in fact it should be msec ;)
When heavy load it still occurs but far less frequently,
The HTTP specification states every request shall receive a response.
Your backend closes the connection while nginx is awaiting/reading the
headers.
The problem definitely comes from your backend. You could use tcpdump
between nginx and your backend to record what they say to each other.
Try to
My config btw:
user imail;
worker_processes auto;
daemon on;
master_process on;
error_log logs/mos_error.tcp debug_tcp;
error_log logs/mos_error.log;
pid/opt/imail/nginx/logs/mos_nginx.pid;
worker_rlimit_nofile 20;
worker_rlimit_core 500M;
working_directory /opt/imail/nginx;
e
ot;, upstream:
"http://10.45.69.26:8081/", host: "mxosCl:8081"
upstream servers doesn't log any issues, it seems. clients get a 502 Bad
Gateway for such requests.
TIA
/Steffen
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello Maxim,
Thank you for the response. I was assuming the error_log in the block
was properly set up but apparently it was not. I finally got an error
message "2015/12/10 18:02:13 [error] 30341#0: *10 recv() failed (104:
Connection reset by peer) while reading response header from
upstream". Pro
Hello!
On Wed, Dec 09, 2015 at 05:03:56PM +0100, Christ-Jan Wijtmans wrote:
> Hello,
>
> I have a magento website working fine for months now.
> However i recently installed a PDF plugin to send invoices with emails.
> The PDF url is giving a 502 bad gateway
> "{ad
Hello,
I have a magento website working fine for months now.
However i recently installed a PDF plugin to send invoices with emails.
The PDF url is giving a 502 bad gateway
"{admin}/sales_invoice/view/invoice_id/717/key/5650a40d93929f5db4383db2a169b08a/".
I have checked around on the in
Greetings,
I'm trying to get a C compiled program to work using fcgi with nginx, but I'm
showed a 502 Bad Gateway.
The actual setup is : all programs in ./cgi-bin/*.cgi should use fcgiwarp. The
actual result is every adress matching report 502 Bad Gateway.
I'm not sure of what
Hello!
On Sat, Aug 02, 2014 at 05:09:54AM -0400, shobhit wrote:
> We are using nodejs(v 0.10.29 ) ,express,nginx( version 1.4.6) with
> mongodb(v 2.6.3) replicaset and getting intermittent 502 bad gateway error.
> pm2 logs is unable to log error though nginx aerror.log is showing
>
We are using nodejs(v 0.10.29 ) ,express,nginx( version 1.4.6) with
mongodb(v 2.6.3) replicaset and getting intermittent 502 bad gateway error.
pm2 logs is unable to log error though nginx aerror.log is showing
recv() failed (104: Connection reset by peer) while reading response
header from
Solved:
It was my bad I had domain without ssl binded to same port as this one with
ssl. So it wasn't working.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,249059,249095#msg-249095
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx
Hello!
On Mon, Apr 07, 2014 at 07:38:00AM -0400, zajca wrote:
> I'm trying to make work nginx 1.4.7 with nodejs websockets
> but I'm getting 502 bad gateway
>
> NGINX Error:
> [error] 2394#0: *1 upstream prematurely closed connection while reading
> response
I'm trying to make work nginx 1.4.7 with nodejs websockets
but I'm getting 502 bad gateway
NGINX Error:
[error] 2394#0: *1 upstream prematurely closed connection while reading
response header from upstream, client: 127.0.0.1, server: xxx.cz, request:
"GET / HTTP/1.1", upstrea
On Fri, Nov 15, 2013 at 05:58:41PM -0500, justin wrote:
> Can you link to the stackoverflow posts? I wish php-fpm told me what
> happened.
See, my memory. =8-((
It was this link that helped me most:
http://forum.nginx.org/read.php?11,215606,235395
Cheers,
--Toni++
Hey Tony.
Can you link to the stackoverflow posts? I wish php-fpm told me what
happened.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,244669,244724#msg-244724
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo
On Thu, Nov 14, 2013 at 01:13:08PM -0500, justin wrote:
> My PHP application went down for a few hours with 502 bad gateway. In the
> nginx error log all I see is:
>
> 2013/11/14 10:02:16 [error] 1466#0: *57964 recv() failed (104: Connection
> reset by peer) while reading respo
My PHP application went down for a few hours with 502 bad gateway. In the
nginx error log all I see is:
2013/11/14 10:02:16 [error] 1466#0: *57964 recv() failed (104: Connection
reset by peer) while reading response header from upstream
I fixed it by restarting php-fpm. However, what caused this
unable to bind listening socket f
darshan.choudhary Wrote:
---
> Did everything you mentioned above but still it is showing after I
> run/etc/init.d/php-fpm start
>
> -bash: /etc/init.d/php-fpm: No such file or directory
I somehow managed to install fpm and now it is not startin
Did everything you mentioned above but still it is showing after I
run/etc/init.d/php-fpm start
-bash: /etc/init.d/php-fpm: No such file or directory
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,239181,239213#msg-239213
___
nginx mailing l
Add those lines to yout /etc/apt/sources.list
#php
deb http://packages.dotdeb.org squeeze all
deb-src http://packages.dotdeb.org squeeze all
than run
apt-get update
apt-get upgrade
apt-get install php5-fpm
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,239181,239212#msg-239212
_
I am using php 5.3.3 and trying to install php-fpm and on research i came to
know that php-fpm come bundled wirh 5.3.3 but still not able to find it.
http://trainingjunction.in/phpinfo.php
where am i going wrong?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,239181,239211#msg-239211
I am using php 5.3.3 but still not able to find php-fpm in it!!
http://trainingjunction.in/phpinfo.php
where am i going wrong?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,239181,239210#msg-239210
___
nginx mailing list
nginx@nginx.org
h
I would suggest using php-fpm, its very easy to setup, in fact its
integrated to recent releases of PHP (5.4++)
On Tue, May 14, 2013 at 11:46 PM, d3f3kt wrote:
> Use this command with the "-C 6" and than you should be happy
>
> Posted at Nginx Forum:
> http://forum.nginx.org/read.php?2,239181,
Use this command with the "-C 6" and than you should be happy
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,239181,239204#msg-239204
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
this is something that i do whenever this happens. and error goes away.
but it happens again. about 3-4 times a day.
is there a way to solve this permanently?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,239181,239194#msg-239194
___
nginx
Oh sorry, that was my fault. I thought you are using php-fpm.
If you are using fcgi than you could use
/usr/bin/spawn-fcgi -a 127.0.0.1 -p 9000 -u www-data -g www-data -f
/usr/bin/php5-cgi -P /var/run/fastcgi-php.pid -C 6
The number after -C is the amount of children.
Posted at Nginx Forum:
http
Hi,
Thanks for the help. It seems I don't have a www.conf in my nginx folder.
This might sound naive but I am not able to find www.conf file.
Upon search, I got to know that it should be in opt folder. But there is
nothing in it.
I have a nginx running on fcgi and Debian Squeeze.
Posted at Ngin
Increase the pm.max_children, pm.start_servers, pm.min_spare_servers and
pm.max_spare_servers in the www.conf
this should help
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,239181,239182#msg-239182
___
nginx mailing list
nginx@nginx.org
http
I am getting a 502 Bad Gateway on my server after any random intervals.
If i run the following code the server starts working again:
/usr/bin/spawn-fcgi -a 127.0.0.1 -p 9000 -u www-data -g www-data -f
/usr/bin/php5-cgi -P /var/run/fastcgi-php.pid
I have tried every possible way available on the
2013/04/13 01:09:06 [notice] 12129#0: signal 29 (SIGIO) received
2013/04/13 01:18:53 [error] 12131#0: *19 open()
"/home/wwwroot/tag/psd-to-html5-volusion-themes" failed (2: No such file or
directory), client: 66.249.73.10, server: www.surilasafar.com, request: "GET
/tag/psd-to-html5-volusion-themes
Log file details.
2013/04/13 00:03:29 [alert] 10931#0: open socket #13 left in connection 3
2013/04/13 00:03:29 [alert] 10931#0: open socket #22 left in connection 14
2013/04/13 00:03:29 [alert] 10931#0: open socket #23 left in connection 15
2013/04/13 00:03:29 [alert] 10931#0: open socket #27 lef
Hello!
On Fri, Apr 12, 2013 at 12:23:53PM -0400, cruise wrote:
> Hello,
>
> I am getting 502 bad gateway error while trying to setup nginx server as
> reverse proxy server with caching enabled. Both servers are on seperate
> machines, another server having apache web server.
&
Hello,
I am getting 502 bad gateway error while trying to setup nginx server as
reverse proxy server with caching enabled. Both servers are on seperate
machines, another server having apache web server.
Given below are my config files, please help me.
nginx.conf
On Mon, Mar 18, 2013 at 08:53:10PM +0100, Yunior Miguel A. wrote:
Hi there,
I see that I was wrong in assuming how thin works.
> thin configuration:
> servers: 1
> socket: /tmp/thin.sock
It looks like the *actual* file name used for the socket can add a
".integer" before the final "." in the c
thin => socket: /tmp/thin.sock
nginx => server unix:/tmp/thin.0.sock;
would be the problem i think.
Am 18.03.2013 20:53, schrieb Yunior Miguel A.:
Thans for all. The end configuration:
thin configuration:
chdir: /var/www/redmine/
environment: production
address: 127.0.0.1
port: 3000
timeout:
Thans for all. The end configuration:
thin configuration:
chdir: /var/www/redmine/
environment: production
address: 127.0.0.1
port: 3000
timeout: 30
log: /var/log/thin/gespro.log
pid: tmp/pids/thin.pid
max_conns: 1024
max_persistent_conns: 512
require: []
wait: 30
servers: 1
daemonize: true
socke
On Mon, Mar 18, 2013 at 05:13:12PM +0100, Yunior Miguel A. wrote:
Hi there,
> I am put the same port and change server unix:/tmp/thin.sock;
>
> and the log is the same.
I'm not sure what exact configuration and log you are looking at in this
test, but if your nginx.conf says "unix:/tmp/thin.so
Whn I am go /tmp/thin.0.sock that file exist. Sometime when i am reset
the thin read thin:
/var/lib/gems/1.9.1/gems/activesupport-3.2.12/lib/active_support/dependencies.rb:251:in
`block in require': iconv will be deprecated in the future, use
String#encode instead.
I am put the same port and c
Hello!
On Mon, Mar 18, 2013 at 04:12:58PM +0100, Yunior Miguel A. wrote:
> I have install nginx 1.1.19 and thin 1.5.0 in Ubuntu 12.04 and I am
> install redmine, when I try to access the page of redmine gives me the
> following error: 502 Bad Gateway. In Nginx log reads:
> 2013/03
On Mon, Mar 18, 2013 at 04:12:58PM +0100, Yunior Miguel A. wrote:
Hi there,
> I have install nginx 1.1.19 and thin 1.5.0 in Ubuntu 12.04 and I am
> install redmine, when I try to access the page of redmine gives me the
> following error: 502 Bad Gateway. In Nginx log reads:
> 2013
I have install nginx 1.1.19 and thin 1.5.0 in Ubuntu 12.04 and I am
install redmine, when I try to access the page of redmine gives me the
following error: 502 Bad Gateway. In Nginx log reads:
2013/03/18 10:45:09 [crit] 13886#0: *11 connect() to
unix:/tmp/thin.0.sock failed (2: No such file or
>
> This server is behind a cisco firewall with port 8080 open. Where is
> the
> problem?
>
> The line:
>
> proxy_pass http://$http_host$uri$is_args$args;
>
> has problem with firewalls? or it is something else?
>
are you able to connect to $http_host from that second server,
maybe via lynx/
second server I get the message 502 bad gateway.
This server is behind a cisco firewall with port 8080 open. Where is the
problem?
The line:
proxy_pass http://$http_host$uri$is_args$args;
has problem with firewalls? or it is something else?
--
Παναγιώτης Θεοδωρόπουλος
Panagiotis
>So: what is the hostname in the url that you try to get, when you see
>the 502 error?
Trying to install a Wordpress, used a info.php page here:
http://blog.koshie.fr/wp-admin/info.php
Ok - so the one server{} block that is used is either the one that has
server_name blog.koshie.fr, or is the
what is the hostname in the url that you try to get, when you see
>the 502 error?
Trying to install a Wordpress, used a info.php page here:
http://blog.koshie.fr/wp-admin/info.php
Ok - so the one server{} block that is used is either the one that has
server_name blog.koshie.fr, or is the de
oshie.fr, or is the default one.
As you can see, there is a 502 Bad Gateway error.
Yes, and that error log shows that:
2013/02/21 10:21:22 [error] 1097#0: *5 connect() failed (111: Connection
refused) while connecting to upstream, client: 46.218.152.242, server:
koshie.fr, request: "GET /wo
> > Dump question, but why did you put the vhost-files into "conf.d"?
> > Normally
> > they are stored in "sites-available" and symlinked in "sites-enabled".
> > nginx
> > (as apache) uses this directory to read all information about the
vhosts.
> > Are there any templates in "sites-enabled"?
k - so the one server{} block that is used is either the one that has
server_name blog.koshie.fr, or is the default one.
> As you can see, there is a 502 Bad Gateway error.
Yes, and that error log shows that:
> 2013/02/21 10:21:22 [error] 1097#0: *5 connect() failed (111: Connection
>
Le Thu, 21 Feb 2013 13:46:35 +0100, Mark Alan a écrit:
On Thu, 21 Feb 2013 12:07:41 +0100, GASPARD Kévin
wrote:
To be honest I don' know. When I've setup this configuration (more
than 1 year ago I think)
It seems that you are trying to force a non Debian directory
structure into a Debian o
1 - 100 of 112 matches
Mail list logo
