I just tried to get into the Neverwinter Gateway, but got this instead. I was able to replicate the issue in Firefox and IE. The regular site is fine for me.
Error: OK, open 'c:\BeholderServer\NightServer\gateway\prod\Night\login\server\public\locale\en\index.html'
at static (c:\BeholderServer\NightServer\gateway\prod\node_modules\connect\lib\middleware\static.js:81:8)
at next (c:\BeholderServer\NightServer\gateway\prod\node_modules\connect\lib\proto.js:199:15)
at module.exports (c:\BeholderServer\NightServer\gateway\prod\node_modules\connect\lib\middleware\compress.js:145:5)
at next (c:\BeholderServer\NightServer\gateway\prod\node_modules\connect\lib\proto.js:199:15)
at c:\BeholderServer\NightServer\gateway\prod\node_modules\cryptic\rewriteForLocale.js:62:11
at fs.exists (fs.js:91:19)
<::::::::::::::)xxxo <::::::::::::::)xxxo <::::::::::::)xxxxxxxx(:::::::::::> oxxx(::::::::::::::> oxxx(::::::::::::::> "Is it better to be feared or respected? I say, is it too much to ask for both?" -Tony Stark Official NW_Legit_Community Forums
mangycheshireMember, Neverwinter Beta Users, Neverwinter Guardian UsersPosts: 0Arc User
edited May 2013
I had to giggle. They're running a professional server that could be easily exploited on a Windows Server box. Not only does that make no sense from a security position, it makes no sense from a performance or stability position. Makes a lot of sense why the gateway is slow as a slug though.
Edit after re-read: If that's not a Windows box, what the heck is up with that folder structure and why on earth would you have an error code that throws that much information about your server structure? That's just silly.
I had to giggle. They're running a professional server that could be easily exploited on a Windows Server box. Not only does that make no sense from a security position, it makes no sense from a performance or stability position. Makes a lot of sense why the gateway is slow as a slug though.
Edit after re-read: If that's not a Windows box, what the heck is up with that folder structure and why on earth would you have an error code that throws that much information about your server structure? That's just silly.
No wonder I got an email stating that a new device accessed my account from the gateway, and the IP was from China, go figure. I run my own server and it is 100x more secure than this, what a joke. It should have thrown a 404 or a 500 error page, but certainly not ANY information, especially directory structure, right down to file names, ugh, very bad.
0
kolbe11Member, Neverwinter Beta Users, Neverwinter Guardian UsersPosts: 0Arc User
edited May 2013
Too many eggs in one basket... And the basket is running on Windowz!
From the file pathing you can tell that the gateway is running on a Windows 2008 Server with IIS and hosts the gateway for all 3 shards.
"It is said that idle hands are the Devil's tools: Idle geek hands, however, came up with gunpowder, nuclear weapons, and toilet plungers." -Illiad
Too many eggs in one basket... And the basket is running on Windowz!
From the file pathing you can tell that the gateway is running on a Windows 2008 Server with IIS and hosts the gateway for all 3 shards.
Um, yeah, it's like handing partial keys to unlock the lock, for someone that knows what to look for. ;( How dumb. And not to mention that Java Script is quite easy to manipulate.
I had to giggle. They're running a professional server that could be easily exploited on a Windows Server box. Not only does that make no sense from a security position, it makes no sense from a performance or stability position. Makes a lot of sense why the gateway is slow as a slug though.
Edit after re-read: If that's not a Windows box, what the heck is up with that folder structure and why on earth would you have an error code that throws that much information about your server structure? That's just silly.
Custom Errors = 0 probably is your reason.
Smart admins will redirect ANY error to a custom "Sorry, we messed up" link, not print debug info to the end user.
I had to giggle. They're running a professional server that could be easily exploited on a Windows Server box. Not only does that make no sense from a security position, it makes no sense from a performance or stability position. Makes a lot of sense why the gateway is slow as a slug though.
Edit after re-read: If that's not a Windows box, what the heck is up with that folder structure and why on earth would you have an error code that throws that much information about your server structure? That's just silly.
Sounds like you girls run single stand-alone servers. Over 20 years in the industry and the majority of the web-facing stuff I see seems to be load-bal farms of IIS on windows. It's scalable and cheap and works perfectly well if hardened properly and your code is solid. Oh yeah slowloris FTW.
In an effort to get this back on topic... Waiting for next update!
Gateway is now unlocked after we addressed a few issues. The Neverwinter Team will continue to monitor it for any new potential issues. Thanks for your patience and understanding.
Comments
Though on the Twitter feed, they say they're working on it.
D&D Home Page - What Class Are You? - Build A Character - D&D Compendium
Edit after re-read: If that's not a Windows box, what the heck is up with that folder structure and why on earth would you have an error code that throws that much information about your server structure? That's just silly.
No wonder I got an email stating that a new device accessed my account from the gateway, and the IP was from China, go figure. I run my own server and it is 100x more secure than this, what a joke. It should have thrown a 404 or a 500 error page, but certainly not ANY information, especially directory structure, right down to file names, ugh, very bad.
From the file pathing you can tell that the gateway is running on a Windows 2008 Server with IIS and hosts the gateway for all 3 shards.
Um, yeah, it's like handing partial keys to unlock the lock, for someone that knows what to look for. ;( How dumb. And not to mention that Java Script is quite easy to manipulate.
Custom Errors = 0 probably is your reason.
Smart admins will redirect ANY error to a custom "Sorry, we messed up" link, not print debug info to the end user.
Sounds like you girls run single stand-alone servers. Over 20 years in the industry and the majority of the web-facing stuff I see seems to be load-bal farms of IIS on windows. It's scalable and cheap and works perfectly well if hardened properly and your code is solid. Oh yeah slowloris FTW.
In an effort to get this back on topic... Waiting for next update!