quot;, upstream: "fastcgi://unix:/var/run/php/php7.0-fpm.sock:", host:
> "fp-academy.in", referrer: "https://fp-academy.in/stage/";
(This does not address any of the nginx config; but it's simplest to
fix one thing at a time. Maybe there is only one thing
030w,
> %20https://fp-academy.in/stage/wp-content/uploads/2019/11/hp_slider_bg-1500x797.jpg
> 1500w,
> %20https://fp-academy.in/stage/wp-content/uploads/2019/11/hp_slider_bg-705x375.jpg
> 705w" sizes="(max-width: 1600px) 100vw, 1600px" />
It
ded after them.
"""
> Can one also remove certain arguments from the query string this way?
Not easily, this way.
For that, you probably want either to use one of the embedded languages
to manipulate things; or to use the module referenced in the other
e 20% was being
> sent in the URL.
And thanks for sharing the eventual fix -- that will probably help the
next person with the same issue.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailm
es nginx generate this outgoing
Host: header?", or "why does nginx not handle this incoming Host: header
the way I want it to?", or something else entirely.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
ng
in one location{} block, that presumably uses "proxy_pass". There may
also be "proxy_set_header" directives, possibly from an "include",
and possibly inherited into this location{}.
The config may show where the unwanted part is being introduced.
Cheers,
f
--
Fr
ased
manipulation to make things work the way that you want. I suspect that
either of those is likely to be more work in the long run than fixing
the upstream.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
php code say "send a 301" or "send a 302"?
Can you change it to say "send a 301", if you want a 301?
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
{"
add
if ($slug_city) { return 301 /location/$slug_city; }
That may or may not be clearer to whoever is going to maintain the system
in the future.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
of your body filter is cached by the
first nginx.
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
haps the service was not running; perhaps it was blocked by a firewall;
perhaps it was overloaded and protected itself by blocking the connect
attempt.
The logs for the port-3000 service might give more a hint of why nginx
failed to connect then.
Good luck with it,
on IIS, then it will not work
through any proxy or reverse proxy (unless it has specific ntlm support).
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
request
that gets a response that you do not want, that may help make it clear
where the problem is.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
st, then that should be changed in vue.
I suspect that almost anything in the vue config that mentions localhost,
should be removed. But vue people may be a better source of information
there.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
.
That comes from the following (lines removed):
> autocomplete="off" >
> aria-label="username" tabindex="1" autocapitalize="none" />
> type="p
ests.
What does "curl -vk" show? That will make a GET request.
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
uot;return" line to include "https://this-server$hugo_url";,
if you want that.)
(If all of your "old" requests have the same content from the first /
to the ?, then you could choose to isolate the "if" within the matching
"location = /" block for efficie
t file --
I think that the request "/?p=1234" serving the content of the file
"/usr/local/nginx/html/?p=1234" is unlikely to be an initial default in
many web servers.
Hopefully you now have a system that works for you and needs no ongoing
maintenance.
Cheers,
nt, invites the browser to
try to access localhost.
*That* is the thing that needs to be changed. If you can see where it is,
then maybe it will be clear how to change it.
Good luck with it!
f
--
Francis Dalyfran...@daoine.org
___
d some nginx proxy_redirect lines; or
you need to change the vue setup to never use the word "localhost". Or
maybe both.
If you can show where the word "localhost" appears in the response to the
request for ggc.world, it may be clearer where the change should be made.
f
--
nd, presumably, send it to nginx).
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
that
it (probably) asks for /sockjs-node/info instead.
Exactly how to do that is probably in the vue documentation.
I see no evidence of a nginx config problem here, so far.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
t* 400, you can do
error_page 494 =400 /my4xx.html;
or, possibly for the specific case of 494,
error_page 494 =431 /my4xx.html;
Hope this helps,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
eems to work for me.
Can you show one request and the matching incorrect response?
Small is good; something like
curl -v http://examplesite.com/new/a.js
should work -- the matching file a.js in the 172.22.3.16:8000 document
root should have suitable content.
curl -v http://172.22.3.15/a.
liably.
If "unreliable" is good enough for you, then carry on. Otherwise, come
up with a new requirement that can be done.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
quot;|
grep include" or "| grep '^# con'" -- to see what file are read.
Without a working config file, something like "grep include nginx.conf"
can show the first set of extra files that will be read. Duplicates
there are probably bad.
Good luck with it,
ing for crypt() in libcrypt ... found
There is more information (probably) in objs/autoconf.err
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
here, other than what was previously
mentioned.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
/x/wordpress/wp-admin/index.php in the first case, and
/x/wordpress/load-styles.php in the second.
Why do the first rewrites exist? Are they breaking your setup?
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
you might be happier still, replacing the three lines with something
like
try_files $uri $uri/ /site/index.php;
which is the usual nginx way to "fall back" to php processing.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
__
On Wed, Feb 19, 2020 at 06:30:39PM -0500, AshleyinSpain wrote:
> Francis Daly Wrote:
> > On Thu, Feb 06, 2020 at 06:02:50PM -0500, AshleyinSpain wrote:
Hi there,
> > > I am trying to block direct access to any URL with a directory
> > /radio/
> > >
> > &g
meters in the php config of my server that I need
> to change?
Maybe.
But guessing may not be the most efficient way to resolve the problem.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
be-blocked"
requests get to your back-end. Adjust to taste based on testing.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Tue, Feb 25, 2020 at 05:06:15PM +, Francis Daly wrote:
> On Tue, Feb 25, 2020 at 07:05:05AM -0500, stmx38 wrote:
Hi there,
two corrections to my suggestion...
> > For location /test we should permit only POST, for /test?doc we should
> > permit only GET methods.
&
that to "proxy_pass http://django;"; is probably the best
first step.
Maybe there won't need to be a second step!
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
and allow without
> args a then default value is applied. Maybe you can provide more details
> here.
Yes, the order is important. Per the docs: the first matching regex is
the regex that counts.
So - if you have some things which are subsets of some other thin
ginx.conf:8
nginx: configuration file /usr/local/nginx/conf/nginx.conf test failed
So - no.
Is there a reason why you might want that? Perhaps the thing that you
want to achieve can be done some other way?
Cheers,
f
--
Francis Dalyfran...@daoine.org
_
n to the server "xxx.it"
> Contact the system administrator for more info.
What do the nginx access log and the nginx error log show when this
happens?
Perhaps that will help show where the first problem is.
(Perhaps the dav_ext_methods directive should be uncommented?)
Cheers,
oes proxy_pass to something else, does *that* do something
different with a GET and a POST?
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
tps://backend.example.com:443/getsomething";, host: "nginx_server_ip"
I believe that that says that nginx (as the client) does not accept the
certificate provided by the server at backend.example.com; probably due
to nginx's proxy_ssl_tru
://localhost/index.php, not http://localhost/public_html/index.php.
But that will only matter after the current error is resolved.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
http to it.
> nginx version: nginx/1.13.5
> Can anyone help me in this regard how to fix this issue?
Either - make your port 6667 listener use http, not https; or tell nginx
to talk https to it.
f
--
Francis Dalyfran...@daoine.org
__
side (and the error log, possibly
in debug mode for the test), to see what nginx did with the request that
involved it *not* making the fastcgi_pass request.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing l
s that you are mixing different
conventions.
That is perfectly fine; nginx does not care what you do, so long as you
can tell it what you want it to do.
To simplify things, I suggest you put *everything* that you care about
in public_html, and use that as the only "root" set at "server
pecific test case that shows this problem?
==
stream {
server {
listen 9001;
proxy_pass 127.0.0.3:22;
}
}
==
and "ssh -v -p 9001 localhost" would seem to indicate that it Just Works.
Perhaps my testing is wrong?
f
--
Francis Dalyfran...@daoine.org
___
ine for a request that has a
silly-long referer: header.
Is this the only such line in your log file? Can you track previous
requests from this same browser/user to see if there is a real problem
that you can address?
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ml as the
document root for requests that end in .php.
The request /js/dragdrop.js is not handled in this location. The
configuration in, or inherited into, the location that handles
that request is the one that matters. And that, presumably, has
/home/ubuntu/htdocs as the configured
quot;curl -v") to make
the request? That is less likely to hide important information.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
(At least, not without writing your own special-case caching system.)
What is the thing that you want to achieve? Perhaps there is an alternate
way to get to the same desired end result.
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
for you to make sure that
server1 and server2 both have the same shared idea of a session, so that
the same cookie sent to either server will end up with the same response.
And there is nothing the nginx can do about arranging that.
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
igin ndoe loads it fine.
What is the difference in the output between requests like
curl -i http://nginx-server/example.svg
and
curl -i http://origin-server/example.svg
?
That difference might hint where the problem is caused.
f
--
Francis Daly
Presumably -- it will be one of the things that is different between the
"good" and the "bad" responses.)
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
er should not be the case, if you are using the same client to
access both urls -- it should be getting the same content in both cases.)
You may want to investigate why your nginx is sending duplicate headers.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ably thinking that you are disabling the facility instead.
Perhaps "error_log off;" is used?
nginx -T | grep off
may show it; then repeating "nginx -T" and finding the context should
show you which file/line is involved.
"
and/or "proxy_set_header" and friends, to ensure validation work as
it should.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Wed, Apr 08, 2020 at 05:12:59AM -0400, lsces wrote:
> Francis Daly Wrote:
Hi there,
> > I'm not quite sure where "the thing that handles the /auth/auth.php
> > request" is running. "proxy_pass" is for "something other than this
> > serv
that does what you need it to.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
non-trivial to reverse-proxy a service at a
different places in the url hierarchy from where the service believes
it is located. Sometimes a different approach is simplest.
> server {
>
> # automatically sets to https if someone comes in on http
> listen 80;
> listen 8
may be simpler to
maintain that list twice than to use another "include" file.
If you are happy to test and report what fails, then it should be possible
to end up with a suitable config.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ing;
or change the return line to be
return 307 $scheme://$host$my_uri_to_lowercase$is_args$args;
http://nginx.org/r/$is_args and http://nginx.org/r/$args for details.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
_
proxy_set_header Origin "";
> proxy_pass https://192.168.1.20:80/;
> auth_basic off;
> }
I don't actually know if a websocket connection will pass cleanly through
two reverse proxies. I guess this is
the list; that will hopefully
help the next person with the same problem find it more quickly :-)
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
https not http.
You can have both "listen" directives in the same server{}, but you
still must use the correct protocol on each port, or there will be errors.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
ngi
etc/webmin/config on host2
and then change your config to only use one trailing slash like so:
location /host1/ {
proxy_pass https://host1.local.domain:1;
And if there is still a problem, if you can show the request/response that
does not do what you expect, it may be simpler
On Tue, Apr 28, 2020 at 02:56:09PM -0400, Paul wrote:
> On 2020-04-22 3:14 a.m., Francis Daly wrote:
Hi there,
> Thanks. I have the two sites "mostly" working now (full config below), but
> could you please expand on your comment ""listen 8001 ssl;" means that
sever on my Nginx hostsystem. Not on vml32.
>
I suspect that that is because you used the line
proxy_set_header Host $host;
When the rest is working, you can perhaps try to log in using credentials
that are different on the two servers, and see which lets you in.
do you want?
* what response do you get instead?
Possibly there will be something interesting in the IIS server logs too.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Mon, May 11, 2020 at 10:24:49AM -0400, MarcoI wrote:
Hi there,
> I'm trying to figure out how to load static files .
What request do you make?
What file on your filesystem do you want nginx to return, in response
to that request?
f
--
Francis Dalyfran...@da
the header. And "always"
is because you probably only get the WWW-Authenticate on a 401 response.
http://nginx.org/r/map
http://nginx.org/r/$upstream_http_
http://nginx.org/r/add_header
(Note the standard caveats about directive inheritance, particularly
regarding add_header, if
pm_backend;
> break;
> }
> }
Maybe does not matter here; presumably the person who published the
config believes it is necessary.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
hen if the response is
http 200 plus half the intended body, that is what the client will get.
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
mething I consider a problem.)
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
cluding proxy_pass
}
You could use "location ^~ /api/configuration", if you want to allow
anything with that prefix.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
m wondering if nginx can
> postpone the sending of upstream header in any ways?
Can you show the request that you make and the response that you get
that is not the response that you want?
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
__
from an
> Nginx point of view?
Objectively, using run-time variable substitution means that nginx does
more work on every request than it would do without that.
And nginx testing one or two extra "if" statements on every request
means that nginx does more work than it would do with
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
er; but it sounds like it works
well enough as-is.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
t;index.php".
If that does not show the problem -- can you show the response headers
coming from upstream to nginx? That might indicate if the pages are not
being cached by nginx.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
ng
-Control-Allow-Origin’ header is present on the requested
> > resource.
In your "drupal" nginx config, if the request is handled in the "php"
location, there is no Access-Control-Allow-Origin header added.
You might want the "add_header" line there instead.
G
On Thu, May 28, 2020 at 08:16:43PM +0530, Kaushal Shriyan wrote:
> On Thu, May 28, 2020 at 6:11 PM Francis Daly wrote:
> > On Thu, May 28, 2020 at 12:50:34PM +0530, Kaushal Shriyan wrote:
Hi there,
> > In your "drupal" nginx config, if the request is handled in the &qu
proxy_pass http://prd_exemple_teste;
> proxy_read_timeout 60s;
Maybe make that bigger than 60s.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
her
directive is probably a bad idea, especially if you get a http 421 response
from your upstream?
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Tue, Jun 02, 2020 at 10:22:06PM +0300, Maxim Dounin wrote:
> On Tue, Jun 02, 2020 at 04:27:28PM +0100, Francis Daly wrote:
Hi there,
Thanks for the extra information.
> > That suggests that if you choose to use "proxy_ssl_server_name on;",
> > then you almost cer
vestigate measuring tools for your system,
while waiting to see if there is a more specific answer provided on
the list.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
p; }
That looks like it is probably the "standard" close-enough equivalent;
but obviously some part of it does not work in this case.
> And none works
What request do you make?
What response do you get?
What response do you want to get instead?
t you want.
What response do you get?
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
can lead to subtle problems.
ModSecurity-nginx is, I think, not a stock-nginx module. What other
modules are you using?
Often the nginx config can help identify a problem too; it is not clear
to me if that will help in this case.
Good luck with it,
f
--
Francis Dalyfran...@d
design has the
client and the server speaking the same protocol with each other.
An alternative way of proxying smtp is described at
https://docs.nginx.com/nginx/admin-guide/mail-proxy/mail-proxy/
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
mail_*" modules are grouped together.
For a lot of this, if the documentation is unclear, you may be better
off building a test system and seeing what happens when you try things.
If that results in the unclear documentation being made clear, that
is good.
Good luck with it,
ork with minimal extra configuration.
If the protocol is more complicated, then there may need to be a
protocol-specific module involved.
A quick web search does not show me any obvious corba-related nginx
modules.
Good luck with it,
f
--
Francis Dalyfr
that if you want to report on how that patch works for you --
being aware that it was written for an older version of nginx, so possibly
will not apply as-is to the current version -- and/or describe your
specific use case, then there may be someone willing to updat
ed just before your nginx stopped responding? That might
help make a reproduction case, which might in turn help isolate where
the problem is.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
ot; traffic-forwarder (as "stream" mostly is) will probably
not be able to reliably proxy things that use my protocol.
For the specific protocols you care about: can they be proxied?
I suspect that the list will be interested in the results of your testing,
if you are w
m yourself?
Good luck with the investigations! (Presuming that the update to 1.19.1
didn't make it all just start working.)
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
.
> Nginx Conf:
>
> stream {
> upstream backend {
> server backend1.example.com:12345;
>}
>
> server {
> listen 8091;
> proxy_pass backend;
> proxy_ssl on;
Match the
> I would really appreciate any type of help.
I suspect that people who are able to help, will find it easier to help
if they have a full clear question, possibly with sample code.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
ngin
will auto-expire without needing to be purged?
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
some of "reply.responseBody" from the first subrequest as
part of the second subrequest.
Maybe that can be adapted to what you want?
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.or
d by a remote service, then
you'll need to make sure that your nginx can speak whatever protocol
your remote service speaks. Often that is http, using nginx's proxy_pass
directive. (Although in that case, nginx isn't accessing files; it is
receiving the response of a http request
201 - 300 of 1833 matches
Mail list logo
