7. ae-9.r25.tokyjp05.jp.bb.gin.ntt.net 65.7% 36 123.5 98.4 70.9 123.5 24.6

rtt min/avg/max/mdev = 120.106/122.300/123.883/1.651 ms

(Quote)

IP Address: 123.154.255.123 *

> /123 32

/123 32

123.205.17.X - - [19/Feb/2014:21:22:52 -0600] "GET / HTTP/1.1" 200 "-" "Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET

Yeah, which means you can load your backup file and access the nginx directory listing via 123.12.12.13:15701. If you don't have any other requirements go for LES. 3GB of space should also suffice for

Thanks for all the responses. I think for me the most straight forward solution is moving my DNS from 123-reg to cloudfare/afraid, wait for the propagation, ask for my VPS host to move node, then plug

There's also a 123 page thread on them in WHT.. and not for a good reason

Last login: Thu Feb 13 20:32:02 2014 from 123123.dyn.telefonica.de

> 10 123 ms 122 ms 123 ms ae-6.r00.sngpsi02.sg.bb.gin.ntt.net [129.250.6.105]

5 210.213.128.61.static.pldt.net (210.213.128.61) 26.123 ms 29.572 ms 29.726 ms

(Quote)

5*24+3=123 Hours Uptime

rtt min/avg/max/mdev = 120.106/122.300/123.883/1.651 ms

@123Systems ticket：123-U0A7U-YHL,please ！

(Quote)

(Quote)

(Quote)