Did i somehow set up my own webserver?

What does " i cannot run the website" mean exactly?

Can you not access it on a browser?

What happens when you try?

Was it working before?

FYI, the URL works fine for me, Leisure Residence in Canton Valais.

OS X includes the Apache 2 web server you can activate at any point. However this would be a local web server, and unless you've configured your router would not be available outside your own network.

Having a local webserver has nothing to do with your hosted website somewhere else.

Any website can be hacked, the real question, is why would someone want to? It takes time and effort to hack a site, and it usually demands a purpose, objective or payback. Why would someone want to hack your website, and would anybody know about it that would take the time to do so?

Hello christoffrombern,

Check your hosts file at /etc/hosts. You may have some redirection installed there.

You may have some setting somewhere redirecting the URL to an invalid IP.

Did you modify your computer's Host file at any point?

Have you altered your router settings at any time?

There does not appear to be anything in that hosts file that would modify the IP your website name is pointing to.

If you open a terminal, and type : ping -c 3 www.resthouse-wallis.com and press enter what happens?

Can it resolve the name to an IP? If so which IP?

If should be something in the range of 94.231.94.14

If its not resolving to a correct IP, then you'll need to talk to your Internet service provider. It's possible their DNSs do not have the appropriate IP for your website anymore.

Hello again christoffrombern,

It looks like your server is misconfigured. If you navigate to www.resthouse-wallis.com, it works fine, but not if you go to resthouse-wallis.com. You can't ping either one because the www server is the only part accessible.

For me it works for both www.resthouse-wallis.com, and resthouse-wallis.com.

In fact www.resthouse-wallis.com redirects to resthouse-wallis.com.

Beyond that, IP resolution seems to be correct based on the ping results, so its not a DNS issue. The fact Ping does not get an answer just means the server is probably configured to not answer pings. Nothing wrong with that.

But at this point I am stumped as to why Christof cannot access the website.

Perhaps it has already been fixed. They both work for me too. Maybe it just hadn't propagated yet.

etresoft wrote:

Maybe it just hadn't propagated yet.

Perhaps you are right.