Site (domain) outage update

[TAZMINATOR]

I just logged in and out several times on both the forums and the main page, I did not have any problem logging from main nor forums and i never got a certificate popup

 

That is for Neowin.net which you have no problems.

 

But they were having problems on neow.in (not neowin.net)  you can try and see for yourself.

[RiverCampher]

Not sure if this is just Windows 8.1 users but I had to put www. in front of neowin.net or it doesn't work - can finally get onto the forums! (was going mad as pinging the site worked but dns didn't resolve!) .  So it's:

 

74.204.71.245        www.neowin.net

 

The solution right now is editing the hosts files by adding this line (besides flushing DNS entries on your PC):
 

74.204.71.245		neowin.net

I would make this frontpage as it affects us in waves (it didnt affect me yesterday but today its down for me)

 

 

Good luck to getting the site back up quickly :)

[Gerowen]

Not sure if this is just Windows 8.1 users but I had to put www. in front of neowin.net or it doesn't work - can finally get onto the forums! (was going mad as pinging the site worked but dns didn't resolve!) .  So it's:

 

74.204.71.245        www.neowin.net

 

 

Good luck to getting the site back up quickly :)

I had to do the same on my Linux box so Google Chrome and Firefox would be able to visit Neowin.  I just edited the hosts file.

[riahc3]

Hello,

Not sure if this is just Windows 8.1 users but I had to put www. in front of neowin.net or it doesn't work - can finally get onto the forums! (was going mad as pinging the site worked but dns didn't resolve!) .  So it's:

 

74.204.71.245        www.neowin.net

 

 

Good luck to getting the site back up quickly :)

Im on Windows 8.1 and without the "www." it worked for me. Should work as browsers automatically assume the "www." in front if not specified.

[Torolol]

i use:

C:\>nslookup neow.in

and use the result to modify the hosts file.

[snaphat (Myles Landwehr) Member]

Hello,

Went to that page, logged in, it too kme to the main forum page (logged in), I clicked on this thread in the minispy and again it showed the login button.

I am glad it is a problem on my side, not on Neowin's

It isn't just you. I have the same issue and I'm sure others do as well. Interestingly, people who can't log in (and who neglect to do dns modifications) aren't going to be able to say it doesn't work for them.

[Ian S.]

Well, on neow.in I got the SSL certificate error, member images didn't show up, and the login on neow.in took me to a page that said Sorry, you do not have permission to view that. Logging in through the dedicated login page (not the popup) would only stick for one page, after going into this thread, it would have the login button again. Plus the member images would disappear on every other post or so. I had to result to modifying the hosts file in order to post this comment.

This is what I got: Seems to be a new SSL error page in chrome.

[Torolol]

SSL error was obvious due certificates are designated for www.neowin.net and not neow.in

the same hosts measures can be used for user images, if you can get to know the IP adresses for it.

[DaveLegg Developer]

Logging in through the dedicated login page (not the popup) would only stick for one page, after going into this thread, it would have the login button again.

 

I've checked, it looks like the setting for the cookie domain got reverted, and that's what was causing the logins not to stick when using neow.in.

 

I've changed it to how it should be, and tested again, logins are working properly from neow.in again.

[JTA]

FWIW, OpenDNS evidently has it cached. I never noticed a hiccup trying to access the site. Might change when the TTL expires on the dns entry, though.

[Unrealistic]

I've checked, it looks like the setting for the cookie domain got reverted, and that's what was causing the logins not to stick when using neow.in.

 

I've changed it to how it should be, and tested again, logins are working properly from neow.in again.

Thanks. I can finally login. :)

[LoR*Evanescence]

Not sure if this is just Windows 8.1 users but I had to put www. in front of neowin.net or it doesn't work - can finally get onto the forums! (was going mad as pinging the site worked but dns didn't resolve!) .  So it's:

 

74.204.71.245        www.neowin.net

 

 

Good luck to getting the site back up quickly :)

 

 

I had the same is you on Mac OS 10.9 using Safari.  It also does not work without putting http:// in front of it. If I only typed neow.in it wouldn't work for me either.  Only http://neow.in works when I type that in the address bar, it took me a few tries to get it right. 

 

I also had some issues logging into the forum.  I would log in, then it would tell me I don't have permission to view this page.  I click forum home and I was logged out again.  I figured out that logging in 2 times in a row worked for me.  

[Tha Bloo Monkee]

Neowin.net is still down for me.  You guys must be cheesed, missing out on all this time when you could be collecting ad revenue and such. :/ Hopefully the problem is resolved soon.

[SnoopZ]

I wasn't able to login to neow.in yesterday using the login from the forums as it just put me back at the login page, but this morning i can do it fine.

[riahc3]

Hello,

I've checked, it looks like the setting for the cookie domain got reverted, and that's what was causing the logins not to stick when using neow.in.

 

I've changed it to how it should be, and tested again, logins are working properly from neow.in again.

Thank you for looking into the issue. I can confirm that logins now work.

Even though this is Neowin's fault, I think ICANN should have a way better and faster response time.

Im surprised there isnt anything on the frontpage about this yet.

[Steven P. Administrators]

There isn't anything on the frontpage because people who can already connect to Neowin already know the deal.

[firey]

There isn't anything on the frontpage because people who can already connect to Neowin already know the deal.

 

"If you can read this.. you can connect to neowin.. and are aware it's not working properly."   Yea.. I don't see that being very beneficial.

[Haggis Veteran]

Hello,

Thank you for looking into the issue. I can confirm that logins now work.

Even though this is Neowin's fault, I think ICANN should have a way better and faster response time.

Im surprised there isnt anything on the frontpage about this yet.

 

 

If people can access the front page there is no real need for them to read why they cant access the main page

 

There are notifications on Facebook and Twitter

 

:)

 

also if you google Neowin down it will also tell you why :)

[+Mirumir Subscriber¹]

Ola amigos!

 

I've been missing you all! <3

 

I'm curious, will the new posts (made @ neow.in) carry over to the normal site?

[Steven P. Administrators]

I'll do an update once the domain is back in our account.

Ola amigos!

 

I've been missing you all! <3

 

I'm curious, will the new posts (made @ neow.in) carry over to the normal site?

Yep.

[+Mirumir Subscriber¹]

Yep.

 

That's cool.

 

Am I correct to assume that, right now, we're accessing the same physical database, that this isn't a clone of Neowin, but the actual live server with a new domain name?

 

At first, I hesitated to enter my password here because I instantly recalled those web banking spoofing sites :D

[Steven P. Administrators]

DaveLegg (server manager) owns neow.in and made it possible to connect to the database while logging in. It's already used as our shorturl for Twitter.

[+Kyle Subscriber¹]

At least I can still get my daily Neowin fix. *twitch

 

Time for us to bombard ICANN with complaint letters.

[+InsaneNutter MVC]

also if you google Neowin down it will also tell you why :)

I found this from 2003 when i searched for Neowin Down - Neowin shut down

 

I remember that well, very glad to that 10+ years after that Neowin is still around and better than ever :)

 

 

 

This morning when I woke up I was met with an array of problems on the site due to the fact that a member was threatening DoS (denial of service) attacks towards Neowin. This has become a tiring re-occurring problem on Neowin since January instigated by a kid with too much power and no sense to put those skills to a good cause. Despite pleas with hosts and authorities this kid has got away with his unlawful activities against Neowin and many other sites (some affiliated with neowin) and continues to control a large botnet. Due to the fact that this kid has again seen fit to use his army of bots against my site and we are powerless to stop it we have decided to close down. We informed Rackshack to power down our server until further notice

 

This decision wasn't easy, Neowin has been my life for the better part of 3 years, We have dedicated that time to help people and to help people stay informed about the latest news and releases for the IT sector. We don't get paid, we don't force anything on our members yet we are treated like this by a kid who doesn't even know us personally.

 

I am sad that one child can have so much influence on the web that he can destroy a service we offered for free to over 30,000 registrations. I have posted his details on our Neowin MSN community, you can view that here. I just want to close this message by saying thanks for your continued support over the last 3 years.

 

Neowin Admins

 

[Steven P. Administrators]

Heh I remember that!