36if((flags & NGX_HTTP_UPSTREAM_CREATE) && uscfp[i]->port) { 37ngx_log_error(NGX_LOG_WARN, cf->log, 0,"upstream \"%V\" may not have port %d in %s:%ui", 38&u->host, uscfp[i]->port, uscfp[i]->file_name, uscfp[i]->line); 39returnNULL; 40} 41if(uscfp[i]->por...
Than you have to also adjust thematomo.conffile. In this case, change the first part into: upstream php-handler { server my-matomo-app:9000; } The important thing is thatmy-matomo-apphas to be the same service name as defined in yourdocker-compose.ymlfile. ...
nginx-proxy_1 | forego | starting dockergen.1 on port 5000 nginx-proxy_1 | forego | starting nginx.1 on port 5100 nginx-proxy_1 | nginx.1 | 2017/05/31 17:50:48 [emerg] 22#22: invalid number of arguments in "upstream" directive in /etc/nginx/conf.d/default.conf:49 nginx-proxy...
with an optional port, or as a UNIX-domain socket path specified after the “unix:” prefix. If a port is not specified, the port 80 is used. A domain name that resolves to several IP addresses defines multiple servers at once.
In order for this parameter to work, it is necessary to specify the resolve parameter for the server and specify a hostname without a port number. If the service name does not contain a dot (“.”), then the RFC-compliant name is constructed and the TCP protocol is added to the ...
If you have: "UpstreamPathTemplate": "/gateway/notify/{catchAll}" in configuration, Ocelot won't find/notify/negotiateneither on the local machine, nor in the docker container, because there is no match. It looks like you're testing/gateway/notify/negotiateon the local machine and/notify/ne...
Get a shell in the running nginx-proxy container using docker exec: docker exec -it <container_name_or_id> bash and inspect default.conf: cat /etc/nginx/conf.d/default.conf There may be reason written in the comment. In my case when I had a similar problem, nginx-proxy container simpl...
I'm not sure I get what's wrong, it looks like it's an nginx error. Can we add configs (it looks like fastcgi_buffers / fastcgi_buffer_size could help). Or is there a way to control these headers ? On some other working routes, I can see a lot of informations under Cache-Tags...
OK, I have an idea and it happens to work (but I'm not sure why): I removed the -exposed-only from the docker-gen options and it starts working. Note that: The target docker has an exposed port nginx-proxy work with exactly the same container ...
Assuming so, I believe there's always going to be a race condition (helped by but not entirely fixed by#2871) where Envoy may reuse the connection before processing the FIN. In your case it looks like you're sending HTTP/1.0 responses where the connection should not by default be reused...