![]() ![]() Proxy_set_header X-Forwarded-Host $server_name Proxy_set_header X-Forwarded-Proto https ![]() I've setup a reverse proxy to phpmyadmin with the following block: Note: only one port is allowed to be open for this service! I tried adding define( 'REDIRECTION_DISABLE', true ) to my wp-config.php but the error persisted. I attempted to solve this problem by adding this line to my nginx+wordpress configuration:Įrror_page 497 301 =307 It solved the incorrect protocol problem but introduced a new one: now when trying to access my wordpress administration panel through METALLB_IP:5050/wp-admin I get 'ERR_TOO_MANY_REDIRECTS' - I assume it's because wp-admin does it's own redirection which causes an infinite loop. Nginx+wordpress server is listening on a nonstandard port 5050 configured to use ssl so when I try connecting directly to this server via METALLB_IP:5050 I get an error 'The plain HTTP request was sent to HTTPS port' which is expected since the browser has no way of knowing that the server is expecting an https request. I have a couple of problems with this configuration: ![]() So - in spite having two separate networks and all services having different names there seems to be a collision.I have a kubernetes cluster configured as follows:Īll services share a common external metallb IP. Unfortunately, the exact same problem occurred. (The opposite problem occurs when starting b before a).īy the way - I also tried a setup with to separate networks "a" and "b" instead of connecting to the "default" network (I thought that maybe my problem was that both site's databases were hosted on the same network). However, after starting docker/b/docker-compose.yml, I get the nasty #2002 error when trying to login at db.b. If i start docker/a/docker-compose.yml, before docker/b/docker-compose.yml I can with no issue login to a's database from phpmyadmin at db.a. To clarify, the same example as i posted before is still valid: So to summarize, now both the site works "alone" but when both are running, I can only access the database which is connected to the site i start first. So again, I am wondering what I'm missing. (The opposite problem occurs when starting b before a).Īt first I thought i could solve it by starting two separate networks - a and b (instead of using "default" one on both sites). However, after starting docker/ b/docker-compose.yml, I get the nasty #2002 error when trying to login at db.b. ![]() However, only the site that is started first can be properly accessed from phpMyAdmin.Įxample: If i start docker/ a/docker-compose.yml, before docker/ b/docker-compose.yml I can with no issue login to a's database from phpmyadmin at db.a. The proxy and both of the two systems are startable, and i can reach the sites a. and b. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |