Can't access by IPV6
-
Edit 2 I'm a muppet, as I have an identical nginx rule on my Web server I shouldn't be passing the full route only the method to the controller from my local box server { listen 9666; listen [::]:9666; location / { This what I had on local box and is wrong. proxy_pass mysite.com:9666/api/MyController/ What I have now on local box and is correct. proxy_pass mysite.com:9666/ On the Web server I have this. proxy_pass localhost:9654/api/controller/ } } I must have accidentally changed the proxy_pass line on the local box - sorry if I wasted anyones time. "We can't stop here - this is bat country" - Hunter S Thompson - RIP
-
Edit 2 I'm a muppet, as I have an identical nginx rule on my Web server I shouldn't be passing the full route only the method to the controller from my local box server { listen 9666; listen [::]:9666; location / { This what I had on local box and is wrong. proxy_pass mysite.com:9666/api/MyController/ What I have now on local box and is correct. proxy_pass mysite.com:9666/ On the Web server I have this. proxy_pass localhost:9654/api/controller/ } } I must have accidentally changed the proxy_pass line on the local box - sorry if I wasted anyones time. "We can't stop here - this is bat country" - Hunter S Thompson - RIP
The first thing I would do is revalidate the IPv6 configuration on the web server, starting from the network interface, down to the web service configuration. I would also try the
ipv6only=onstatement in the nginx config file, and see whether that makes a difference."Five fruits and vegetables a day? What a joke! Personally, after the third watermelon, I'm full."
-
The first thing I would do is revalidate the IPv6 configuration on the web server, starting from the network interface, down to the web service configuration. I would also try the
ipv6only=onstatement in the nginx config file, and see whether that makes a difference."Five fruits and vegetables a day? What a joke! Personally, after the third watermelon, I'm full."
