Home / user-47706

zengr's questions

Martin Hope
zengr
Asked: 2013-04-16 22:22:06 +0800 CST
  • 0

So I have setup this new website: isitfor.me
It works fine from my browser and I can curl and ping it: 

xMacV2:Telescope zengr$ curl -i isitfor.me
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Date: Tue, 16 Apr 2013 06:19:28 GMT
Content-Length: 639
Connection: keep-alive

But downforeveryoneorjustme.com says its down. who.is also says that the domain is inactive.

What is going on? If the DNS propogation is an issue then I should also see the problem right? But I can browser the url http://isitfor.me from my machine.

domain-name-system
Martin Hope
zengr
Asked: 2011-05-15 14:38:32 +0800 CST
  • 1

hping command: hping3 -G --rroute $domain -i u1000

Result:

len=80 ip=127.0.0.1 ttl=64 DF id=0 sport=0 flags=RA seq=176 win=0 rtt=0.2 ms
       (same route)
len=80 ip=127.0.0.1 ttl=64 DF id=0 sport=0 flags=RA seq=177 win=0 rtt=0.2 ms
       (same route)
len=80 ip=127.0.0.1 ttl=64 DF id=0 sport=0 flags=RA seq=178 win=0 rtt=0.2 ms
       (same route)
len=80 ip=127.0.0.1 ttl=64 DF id=0 sport=0 flags=RA seq=179 win=0 rtt=0.3 ms
       (same route)

--- 127.0.0.1 hping statistic ---
181 packets transmitted, 180 packets received, 1% packet loss
round-trip min/avg/max = 0.2/0.2/0.6 m

So, my question is, what does packets 1% packet loss, 180 packets received and 181 packets transmitted mean?

Update: Question:2:

Command - hping3 -a $ip -S 127.0.0.1 -p 80 -i u1000


len=44 ip=127.0.0.1 ttl=64 DF id=0 sport=80 flags=SA seq=4176 win=32792 rtt=0.3 ms
len=44 ip=127.0.0.1 ttl=64 DF id=0 sport=80 flags=SA seq=0 win=32792 rtt=0.0 ms
len=44 ip=127.0.0.1 ttl=64 DF id=0 sport=80 flags=SA seq=4177 win=32792 rtt=0.3 ms
len=44 ip=127.0.0.1 ttl=64 DF id=0 sport=80 flags=SA seq=0 win=32792 rtt=0.0 ms
len=44 ip=127.0.0.1 ttl=64 DF id=0 sport=80 flags=SA seq=0 win=32792 rtt=0.0 ms
len=44 ip=127.0.0.1 ttl=64 DF id=0 sport=80 flags=SA seq=4178 win=32792 rtt=7.0 ms
len=44 ip=127.0.0.1 ttl=64 DF id=0 sport=80 flags=SA seq=0 win=32792 rtt=0.0 ms
len=44 ip=127.0.0.1 ttl=64 DF id=0 sport=80 flags=SA seq=4179 win=32792 rtt=0.3 ms
len=44 ip=127.0.0.1 ttl=64 DF id=0 sport=80 flags=SA seq=0 win=32792 rtt=0.0 ms
len=44 ip=127.0.0.1 ttl=64 DF id=0 sport=80 flags=SA seq=4180 win=32792 rtt=0.3 ms
len=44 ip=127.0.0.1 ttl=64 DF id=0 sport=80 flags=SA seq=0 win=32792 rtt=0.0 ms
len=44 ip=127.0.0.1 ttl=64 DF id=0 sport=80 flags=SA seq=4181 win=32792 rtt=0.3 ms
len=44 ip=127.0.0.1 ttl=64 DF id=0 sport=80 flags=SA seq=0 win=32792 rtt=0.0 ms
len=44 ip=127.0.0.1 ttl=64 DF id=0 sport=80 flags=SA seq=4182 win=32792 rtt=0.3 ms
len=44 ip=127.0.0.1 ttl=64 DF id=0 sport=80 flags=SA seq=0 win=32792 rtt=0.0 ms
len=44 ip=127.0.0.1 ttl=64 DF id=0 sport=80 flags=SA seq=4183 win=32792 rtt=0.5 ms
len=44 ip=127.0.0.1 ttl=64 DF id=0 sport=80 flags=SA seq=0 win=32792 rtt=0.0 ms
len=44 ip=127.0.0.1 ttl=64 DF id=0 sport=80 flags=SA seq=4184 win=32792 rtt=0.3 ms
^C^C
--- 127.0.0.1 hping statistic ---
4186 packets transmitted, 9184 packets received, -119% packet loss

When I run the above command (after update), I get -119% packet loss, i.e. i receive more packets than I sent. How is that possible? Any quickies on that?

firewall ubuntu ping tcpip
Martin Hope
zengr
Asked: 2010-11-22 16:44:33 +0800 CST
  • 0

I have 1 wild card SSL certificate for 1 domain. But I have multiple servers on sub-domains (server1.domain.com, server2.domain.com etc).

It's only working on the server.domain.com but not on server1.domain.com and server2.domain.com and others.

Is, there any way to fix this and use 1 SSL cert (wildcard for 1 domain) for various servers (hardware)

i.e. if a request for ssl comes on server1.domain.com or server2.domain.com, the request is routed to server.domain.com

Thanks

Error: It says SSL not found in the log file.

I have got this message from my supprt:

You will need to purchase another wildcard ssl as the ssl will only certify one server per ssl.

apache-2.2 ssl configuration