Server Complete

Tracy Perry said:
That would be icing on the cake but true Hardware DDOS mitigation will be hard to find anywhere on a price at that level. Hardware costs alone have to be recouped.
Click to expand...

Indeed, most hosts idea of DDOS mitigation is simple to null route the IP due to the extortionate costs involved in hardware solutions...
 
I have had nothing but a nightmare with them.

First of all I wasn't allowed to wget ANYTHING from a google server (dl.google.com, googlecode, anything.) They blamed this on google using a caching node on their network (which wasn't even being used mind you, so that took 5 days to clear out due to dns and what not.

Secondly I now can't access specific things from my server via googlecode as I get a 403 error as seen below.

Code: 
# wget https://twemperf.googlecode.com/files/mcperf-0.1.1.tar.gz
--2014-02-24 15:49:57--  https://twemperf.googlecode.com/files/mcperf-0.1.1.tar.gz
Resolving twemperf.googlecode.com... 74.125.139.82, 2607:f8b0:4002:c06::52
Connecting to twemperf.googlecode.com|74.125.139.82|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2014-02-24 15:49:57 ERROR 403: Forbidden.

This is nearly 3 weeks it's been like this, they just keep fobbing me off with a "we have a ticket in with google." so my server is just a paperweight.
 
Autonamus said:
I have had nothing but a nightmare with them.

First of all I wasn't allowed to wget ANYTHING from a google server (dl.google.com, googlecode, anything.) They blamed this on google using a caching node on their network (which wasn't even being used mind you, so that took 5 days to clear out due to dns and what not.
This is nearly 3 weeks it's been like this, they just keep fobbing me off with a "we have a ticket in with google." so my server is just a paperweight.
Click to expand...
It may possibly be with your server configuration.
The below was from twowheeldemon.com (which is a server hosted by them)
screenshot.webp
 
Autonamus said:
This is nearly 3 weeks it's been like this, they just keep fobbing me off with a "we have a ticket in with google." so my server is just a paperweight.
Click to expand...

I'd withold payments or dump them, that's some crappy service right there. This is what type of ticket answer I expect from 12 year old (as in age) VPS re-sellers.
 
Autonamus said:
Right, They just don't know how to fix it, it's nothing I have done as it doesn't work after an OS reload.
Click to expand...
My second server with them is giving me the same results you got. Will log into my third one and check it and then compare the different configs. I know I made some changes on them.

EDIT:

The third one also works.... so time to start comparing the 1st one and third one to the second that didn't work. ;)
 
OK... I'm still leaning towards a config error because I was able to get all 3 to work just fine. All I did on the second one was edit my /etc/hosts and removed some domains that were not being used any more and rebooted the server (but don't really see where that would effect it). I also made sure my /etc/network/interfaces were similar in all of them and my /etc/resolv.conf contained the primary server domain name in it. If you notice, each is a different server.

screenshot1.webp screenshot2.webp screenshot3.webp

EDIT:

My alpha.twowheeldemon.com /etc/network/interfaces (this is a ProxMox server)
Code: 
# network interface settings
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
    address  199.48.164.159
    netmask  255.255.255.192
    gateway  199.48.164.129
    broadcast  199.48.164.191
    network 199.48.164.128
    dns-nameservers 208.84.135.10
    dns-search com
# dns-* options are implemented by the resolvconf package, if installed


iface eth1 inet manual

auto vmbr0
iface vmbr0 inet static
    address  23.92.91.161
    netmask  255.255.255.240
    bridge_ports none
    bridge_stp off
    bridge_fd 0

My other two

Code: 
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet static
    address 23.92.80.92
    netmask 255.255.255.192
    network 23.92.80.64
    broadcast 23.92.80.127
    gateway 23.92.80.65
    # dns-* options are implemented by the resolvconf package, if installed
    dns-nameservers 208.84.135.10
    dns-search com

Code: 
# The primary network interface
allow-hotplug eth0
iface eth0 inet static
    address 199.48.164.104
    netmask 255.255.255.192
    network 199.48.164.64
    broadcast 199.48.164.127
    gateway 199.48.164.65
    # dns-* options are implemented by the resolvconf package, if installed
    dns-nameservers 208.84.135.10
    dns-search com
 
D.O.A. said:
I'd withold payments or dump them, that's some crappy service right there. This is what type of ticket answer I expect from 12 year old (as in age) VPS re-sellers.
Click to expand...
Well, considering it's working on all 3 of mine (now - it was 2 working and 1 not working, but with some changes it's now 3) it indicates to me that it may lay more in the server config than on their end. I posted screenshots of all 3 servers doing exactly what he outlined having problems with and you can see they were successful.

@Autonamus, have you tried using the -U firefox parameter with wget to see if it works?
 
Tracy Perry said:
Well, considering it's working on all 3 of mine (now - it was 2 working and 1 not working, but with some changes it's now 3) it indicates to me that it may lay more in the server config than on their end. I posted screenshots of all 3 servers doing exactly what he outlined having problems with and you can see they were successful.

@Autonamus, have you tried using the -U firefox parameter with wget to see if it works?
Click to expand...
Well considering it's a fresh install after a OS reload of CentOS 6 I wouldn't expect any config issues when doing something as simple as connecting to another server to download a file.

Tracy Perry said:
In resolv.conf add two new lines
nameserver 8.8.8.8
nameserver 8.8.4.4
Click to expand...
Adding now.
 
Autonamus said:
Well considering it's a fresh install after a OS reload of CentOS 6 I wouldn't expect any config issues when doing something as simple as connecting to another server to download a file.
Click to expand...
All of mine are Debian based. ProxMox uses Debian as it's base OS (one of the reasons I went with it).

Also, be sure to try the -U parameter and see if that works.
 
Everything seems to work now...

How annoying!

Edit: Spoke too soon, stopped working again.
 
Last edited:
Tracy Perry said:
OK... I'm still leaning towards a config error because I was able to get all 3 to work just fine. All I did on the second one was edit my /etc/hosts and removed some domains that were not being used any more and rebooted the server (but don't really see where that would effect it). I also made sure my /etc/network/interfaces were similar in all of them and my /etc/resolv.conf contained the primary server domain name in it. If you notice, each is a different server.

View attachment 68030 View attachment 68031 View attachment 68032

EDIT:

My alpha.twowheeldemon.com /etc/network/interfaces (this is a ProxMox server)
Code: 
# network interface settings
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
    address  199.48.164.159
    netmask  255.255.255.192
    gateway  199.48.164.129
    broadcast  199.48.164.191
    network 199.48.164.128
    dns-nameservers 208.84.135.10
    dns-search com
# dns-* options are implemented by the resolvconf package, if installed


iface eth1 inet manual

auto vmbr0
iface vmbr0 inet static
    address  23.92.91.161
    netmask  255.255.255.240
    bridge_ports none
    bridge_stp off
    bridge_fd 0

My other two

Code: 
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet static
    address 23.92.80.92
    netmask 255.255.255.192
    network 23.92.80.64
    broadcast 23.92.80.127
    gateway 23.92.80.65
    # dns-* options are implemented by the resolvconf package, if installed
    dns-nameservers 208.84.135.10
    dns-search com

Code: 
# The primary network interface
allow-hotplug eth0
iface eth0 inet static
    address 199.48.164.104
    netmask 255.255.255.192
    network 199.48.164.64
    broadcast 199.48.164.127
    gateway 199.48.164.65
    # dns-* options are implemented by the resolvconf package, if installed
    dns-nameservers 208.84.135.10
    dns-search com
Click to expand...
This is my network interface

Code: 
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet static
    address 199.48.164.166
    netmask 255.255.255.192
    network 199.48.164.128
    broadcast 199.48.164.191
    gateway 199.48.164.129
    # dns-* options are implemented by the resolvconf package, if installed
auto eth0

I also tested Debian just to rule out it being something with CentOS 6 and still nothing.
 
Last edited:
Autonamus said:
This is my network interface

Code: 
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet static
    address 199.48.164.166
    netmask 255.255.255.192
    network 199.48.164.128
    broadcast 199.48.164.191
    gateway 199.48.164.129
    # dns-* options are implemented by the resolvconf package, if installed
auto eth0

I also tested Debian just to rule out it being something with CentOS 6 and still nothing.
Click to expand...
You are missing the two DNS entries in yours compared to the other ones listed

dns-nameservers 208.84.135.10
dns-search com
 
You must log in or register to reply here.

Similar threads

Fullmental
Dedicated server recommendations?
2 3
Replies
50
Views
5K
Vroomm
V
oldford
Help choosing replacement server
Replies
10
Views
1K
oldford
oldford
P
  • Question Question
XF 1.4 VPS Server Compromised: Need Help Restoring Files
Replies
2
Views
470
Phillip
P
Wesker
Server Compromise Issues
2 3
Replies
46
Views
4K
ForumCube
ForumCube
N
  • Question Question
Windows Server Compatibility
Replies
2
Views
741
nattiejim
N
Top Bottom