#1 2017-04-13 20:10:07

Toldierone
Trusted Member
Registered: 2016-06-09
Posts: 40

Gestion DBI - Reverse Proxy down

Hi,
It seems like the reverse proxy server in Montreal (MTL-03) is down since yesterday's reboot to update the kernel.
Pinging the IP of the reverse proxy server from inside of the network yields 100% packet loss.

So I'm just wondering, is it still pending maintenance, or just simply down?
Thanks in advance for clarification.

Offline

#2 2017-04-20 18:01:28

Toldierone
Trusted Member
Registered: 2016-06-09
Posts: 40

Re: Gestion DBI - Reverse Proxy down

h..h-hello?

It's been one week now, and the reverse proxy still isn't accessible, there's still 100% packet loss when pinging the reverse proxy node.
Rebooting the VPS didn't change a thing, in any case.

Can I get any information on the case?

Offline

#3 2017-04-21 13:57:31

DavidGestionDBI
Provider-Moderator
From: Montreal, Canada
Registered: 2015-01-10
Posts: 590
Website

Re: Gestion DBI - Reverse Proxy down

Would be nice that you give your internal IP if you expect help.


-----------
David B. |  Technical Director at Gestion DBI ||  Want to receive our promotions?
IT consulting and Hosting Provider | 24/7 Technical Support

Offline

#4 2017-04-21 15:34:54

Toldierone
Trusted Member
Registered: 2016-06-09
Posts: 40

Re: Gestion DBI - Reverse Proxy down

Oh, right, sorry, my internal IP is 172.21.0.153

Offline

#5 2017-04-21 18:33:52

DavidGestionDBI
Provider-Moderator
From: Montreal, Canada
Registered: 2015-01-10
Posts: 590
Website

Re: Gestion DBI - Reverse Proxy down

Hi,

Can't see any issue with the reverse proxy.
Be sure to follow the step to activate the reverse on: https://www.deepnetsolutions.com/nat-reverseProxy.html


-----------
David B. |  Technical Director at Gestion DBI ||  Want to receive our promotions?
IT consulting and Hosting Provider | 24/7 Technical Support

Offline

#6 2017-04-21 19:29:38

Toldierone
Trusted Member
Registered: 2016-06-09
Posts: 40

Re: Gestion DBI - Reverse Proxy down

Yeah, I've used that exact script to set up the proxy before, but the thing is, I can't use it right now, because it hangs on the POST request (as I said before, I can't even ping the IP address of the node the reverse proxy is on, 100% packet loss).
Also while re-downloading the script from the website, I've noticed that www.deepnetsolutions.com is unaccessible via IPv6 from the VPS, while access via IPv4 works just fine.

ping6 www.deepnetsolutions.com
PING www.deepnetsolutions.com(ipv6.ww1.deepnetsolutions.com) 56 data bytes
^C
--- www.deepnetsolutions.com ping statistics ---
12 packets transmitted, 0 received, 100% packet loss, time 11205ms
ping www.deepnetsolutions.com
PING www.deepnetsolutions.com (104.223.15.200) 56(84) bytes of data.
64 bytes from ww3.deepnetsolutions.com (104.223.15.200): icmp_seq=1 ttl=56 time=66.2 ms
64 bytes from ww3.deepnetsolutions.com (104.223.15.200): icmp_seq=2 ttl=56 time=66.2 ms
64 bytes from ww3.deepnetsolutions.com (104.223.15.200): icmp_seq=3 ttl=56 time=66.1 ms
64 bytes from ww3.deepnetsolutions.com (104.223.15.200): icmp_seq=4 ttl=56 time=66.1 ms
^C
--- www.deepnetsolutions.com ping statistics ---
5 packets transmitted, 4 received, 20% packet loss, time 4042ms
rtt min/avg/max/mdev = 66.135/66.216/66.299/0.321 ms

I think it might be a routing issue.
Should I post traceroutes and routing tables (ie. 'ip route' and 'ip -6 route')?
(Even though I haven't altered those tables in any way)

Offline

#7 2017-04-22 11:30:59

mikho
Low End Mod
From: Hell and gore == Sweden
Registered: 2013-03-02
Posts: 1,297
Website

Re: Gestion DBI - Reverse Proxy down

Toldierone wrote:

I think it might be a routing issue.
Should I post traceroutes and routing tables (ie. 'ip route' and 'ip -6 route')?
(Even though I haven't altered those tables in any way)

 
Wouldn't hurt

Offline

#8 2017-04-22 14:22:12

Toldierone
Trusted Member
Registered: 2016-06-09
Posts: 40

Re: Gestion DBI - Reverse Proxy down

Alright, here's the 'ip route':

169.254.0.0/16 dev venet0  scope link  metric 1002 
default dev venet0  scope link 

and here's 'ip -6 route':

unreachable ::/96 dev lo  metric 1024  error -113 mtu 65536
unreachable ::ffff:0.0.0.0/96 dev lo  metric 1024  error -113 mtu 65536
unreachable 2002:a00::/24 dev lo  metric 1024  error -113 mtu 65536
unreachable 2002:7f00::/24 dev lo  metric 1024  error -113 mtu 65536
unreachable 2002:a9fe::/32 dev lo  metric 1024  error -113 mtu 65536
unreachable 2002:ac10::/28 dev lo  metric 1024  error -113 mtu 65536
unreachable 2002:c0a8::/32 dev lo  metric 1024  error -113 mtu 65536
unreachable 2002:e000::/19 dev lo  metric 1024  error -113 mtu 65536
2607:5300:60:3b6c:33e::/80 dev venet0  proto kernel  metric 256  mtu 1500
unreachable 3ffe:ffff::/32 dev lo  metric 1024  error -113 mtu 65536
fe80::/64 dev venet0  proto kernel  metric 256  mtu 1500
default dev venet0  metric 1  mtu 1500

(venet0 is the default network interface with public IPv6 and internal IPv4 addresses assigned)

traceroutes:

traceroute to 172.21.0.5 (172.21.0.5), 30 hops max, 60 byte packets
 1  mtl03.vmpanel.net (198.50.158.238)  0.104 ms  0.034 ms  0.033 ms
 2  * * *

(then goes * * * until the specified max ttl)

Accessing www.deepnetsolutions.com via iPv6 works today, so that had to be some sort of one-off, but still no luck with the reverse proxy

Offline

#9 2017-04-27 19:50:00

Toldierone
Trusted Member
Registered: 2016-06-09
Posts: 40

Re: Gestion DBI - Reverse Proxy down

Status update, I'm now able to to ping the reverse proxy's IP address.
However I still can't use it, because using the script from https://www.deepnetsolutions.com/nat-reverseProxy.html results in "curl: (7) couldn't connect to host" and

nc -v 172.21.0.5 80
nc: connect to 172.21.0.5 port 80 (tcp) failed: Connection refused

Also, the connection to a domain from outside world also drops with conn refused
(I do have active webserver listening on port 80 on internal IPv4, in any case)

Offline

#10 2017-05-06 05:11:35

Bree871
Member
Registered: 2017-05-06
Posts: 1

Re: Gestion DBI - Reverse Proxy down

I'm having the same issue

Offline

#11 2017-05-11 10:58:33

Toldierone
Trusted Member
Registered: 2016-06-09
Posts: 40

Re: Gestion DBI - Reverse Proxy down

Aaaaand, after one month, it either fixed itself, or you fixed it, as it appears to be working fine now.
One way or another, thanks anyway.

Offline

#12 2017-05-12 14:35:04

DavidGestionDBI
Provider-Moderator
From: Montreal, Canada
Registered: 2015-01-10
Posts: 590
Website

Re: Gestion DBI - Reverse Proxy down

I still don't know what the Dev does to fix it. Waiting on the report myself.


-----------
David B. |  Technical Director at Gestion DBI ||  Want to receive our promotions?
IT consulting and Hosting Provider | 24/7 Technical Support

Offline

#13 2017-05-15 09:43:26

m3h_
Trusted Member
Registered: 2017-05-15
Posts: 3

Re: Gestion DBI - Reverse Proxy down

It seems the reverse proxy is completely down for ZA?
I had sites configured that now respond with

ERR_CONNECTION_TIMED_OUT

when accessed.
When i try to list proxies using the script, I get

curl: (7) Failed to connect to 172.16.60.5 port 80: Connection timed out

A traceroute to 172.16.60.5 shows this...

traceroute to 172.16.60.5 (172.16.60.5), 30 hops max, 60 byte packets
 1  nat1-za01.vmpanel.net (169.239.130.8)  0.103 ms  0.041 ms  0.047 ms
 2  129.232.167.225 (129.232.167.225)  4.586 ms  5.424 ms  5.380 ms
 3  core-access-switch1-v4001.jnb1.host-h.net (197.189.193.33)  3.629 ms  3.592 ms  3.547 ms
 4  core-router2.jnb1.host-h.net (197.189.193.3)  0.372 ms  0.331 ms  0.484 ms
 5  * * *

Any help?

Offline

#14 2017-05-19 13:28:13

m3h_
Trusted Member
Registered: 2017-05-15
Posts: 3

Re: Gestion DBI - Reverse Proxy down

Seems to have started working again, so nevermind!

Offline

#15 2017-05-19 14:03:16

alberth
Trusted Member
Registered: 2017-05-19
Posts: 3

Re: Gestion DBI - Reverse Proxy down

I'm experiencing problems when connecting to the reverse proxy for setup. The reverse proxy web server seems to be offline, though the IP is accessible. My box is in the New Jersey datacenter, and here is the output:

# bash ./NATreverseProxy.sh proxy list
curl: (7) Failed to connect to 172.76.0.5 port 80: Connection timed out
# telnet 172.76.0.5 80
Trying 172.76.0.5...
telnet: Unable to connect to remote host: Connection timed out
# traceroute 172.76.0.5
traceroute to 172.76.0.5 (172.76.0.5), 30 hops max, 60 byte packets
 1  nj02.vmpanel.net (172.93.103.202)  0.188 ms  0.066 ms  0.064 ms
 2  vl182-br2.pnj1.choopa.net (108.61.79.189)  0.267 ms  0.226 ms  0.248 ms
 3  vl23-er1.pnj1.choopa.net (66.55.130.54)  0.247 ms  2.671 ms  2.667 ms
 4  ae5.cr1-nyc4.ip4.gtt.net (69.31.34.209)  0.786 ms ae14.cr2-nyc6.ip4.gtt.net (69.31.34.61)  1.100 ms ae7.cr0-nyc6.ip4.gtt.net (69.31.34.77)  1.013 ms
 5  xe-7-3-6.cr8-nyc3.ip4.gtt.net (89.149.135.177)  1.216 ms  1.225 ms xe-0-1-1.cr8-nyc3.ip4.gtt.net (141.136.110.237)  1.144 ms
 6  * * *
 7  * * *
 8  CITIZENS-CO.ear3.Washington1.Level3.net (4.16.244.58)  7.154 ms  7.099 ms  7.173 ms
 9  ae2---0.cor02.asbn.va.frontiernet.net (74.40.2.177)  28.216 ms  28.163 ms  28.210 ms
10  ae1---0.cor02.chcg.il.frontiernet.net (74.40.2.193)  26.330 ms  26.267 ms  26.291 ms
11  ae0---0.cor01.chcg.il.frontiernet.net (74.40.3.241)  24.154 ms  24.079 ms  24.135 ms
12  ae9---0.car01.ftwy.in.frontiernet.net (74.40.2.146)  26.267 ms  25.953 ms  25.312 ms
13  104.169.205.150 (104.169.205.150)  26.864 ms  26.071 ms  25.972 ms
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Offline

#16 2017-05-19 19:22:58

DavidGestionDBI
Provider-Moderator
From: Montreal, Canada
Registered: 2015-01-10
Posts: 590
Website

Re: Gestion DBI - Reverse Proxy down

Try again.


-----------
David B. |  Technical Director at Gestion DBI ||  Want to receive our promotions?
IT consulting and Hosting Provider | 24/7 Technical Support

Offline

#17 2017-05-21 02:58:45

alberth
Trusted Member
Registered: 2017-05-19
Posts: 3

Re: Gestion DBI - Reverse Proxy down

DavidGestionDBI wrote:

Try again.

Looks like it has now been fixed - thanks for the help!

Offline

#18 2017-08-05 10:36:12

bbn
Trusted Member
Registered: 2017-08-05
Posts: 3

Re: Gestion DBI - Reverse Proxy down

I'm having the same problem:

# ./NATreverseProxy.sh proxy add <my host name>                                      
Sending request to add <my host name>...                                                               
curl: (7) Failed to connect to 172.21.0.5 port 80: Connection refused     

My IPv4 address is 172.21.0.64

Offline

#19 2017-08-05 16:12:47

mikho
Low End Mod
From: Hell and gore == Sweden
Registered: 2013-03-02
Posts: 1,297
Website

Re: Gestion DBI - Reverse Proxy down

bbn wrote:

I'm having the same problem:

# ./NATreverseProxy.sh proxy add <my host name>                                      
Sending request to add <my host name>...                                                               
curl: (7) Failed to connect to 172.21.0.5 port 80: Connection refused     

My IPv4 address is 172.21.0.64

 
Can you ping that IP?

Offline

#20 2017-08-05 21:28:01

bbn
Trusted Member
Registered: 2017-08-05
Posts: 3

Re: Gestion DBI - Reverse Proxy down

I can. I'm not at my pc right now, but if you need any log let me know.

Offline

#21 2017-08-09 18:35:16

DavidGestionDBI
Provider-Moderator
From: Montreal, Canada
Registered: 2015-01-10
Posts: 590
Website

Re: Gestion DBI - Reverse Proxy down

Try to do a telnet on 172.21.0.5:80 and paste the output please.

On my side, everything is up and running.


-----------
David B. |  Technical Director at Gestion DBI ||  Want to receive our promotions?
IT consulting and Hosting Provider | 24/7 Technical Support

Offline

#22 2017-08-11 10:40:43

bbn
Trusted Member
Registered: 2017-08-05
Posts: 3

Re: Gestion DBI - Reverse Proxy down

Here's what I get:

[email protected]:/# telnet 172.21.0.5 80                            
Trying 172.21.0.5...                                                
telnet: Unable to connect to remote host: Connection refused

(I will admit to never have used telnet, but I think that's the right command, since it works with other ips)

If you need (or want to), feel free to ssh in my box. There's nothing there yet smile

Offline

#23 2017-08-31 19:39:23

perice
Trusted Member
Registered: 2016-11-02
Posts: 3

Re: Gestion DBI - Reverse Proxy down

Hey,

same problems as others.

Internal IP: 172.21.0.127

curl: (7) Failed to connect to 172.21.0.5 port 80: Connection refused

telnet 172.21.0.5 80
Trying 172.21.0.5...
telnet: Unable to connect to remote host: Connection refused

Offline

#24 2017-09-08 20:38:08

dsgjezs
Member
Registered: 2017-09-07
Posts: 2

Re: Gestion DBI - Reverse Proxy down

Same result from 172.21.0.168

$ ping 172.21.0.5
PING 172.21.0.5 (172.21.0.5) 56(84) bytes of data.
64 bytes from 172.21.0.5: icmp_seq=1 ttl=64 time=0.153 ms
64 bytes from 172.21.0.5: icmp_seq=2 ttl=64 time=0.068 ms
$ ./NATreverseProxy.sh proxy list
curl: (7) Failed to connect to 172.21.0.5 port 80: Connection refused

Thanks

Offline

#25 2017-09-10 20:55:43

DavidGestionDBI
Provider-Moderator
From: Montreal, Canada
Registered: 2015-01-10
Posts: 590
Website

Re: Gestion DBI - Reverse Proxy down

For people using the MTL proxy, I suggest to swtich to Cloudflare V4 to V6 proxy in the meantime.

Montreal proxy have a lot of issue recently that we try to fix and counting hundred of DDoS attack. For more stability, I strongly suggest using cloudflare.

Regards, David


-----------
David B. |  Technical Director at Gestion DBI ||  Want to receive our promotions?
IT consulting and Hosting Provider | 24/7 Technical Support

Offline

Board footer