VITAS

SpaceDock.info (Mod Hosting Site)

Recommended Posts

im feeling watched :P

because dumb gunicorn (python runtime) is only using one core i did some restructuring based on the idea of having a blanacer and multiple instances of the site runnign on the same server. time will tell if the site explodes less :)

 

first checks indicate: went from 100% on one core to 10% per core with 160 ppl on the site hammering away. so thats a win i would cautiously say :)

Edited by VITAS
  • Like 3

Share this post


Link to post
Share on other sites

Any word yet ? :(

 

Share this post


Link to post
Share on other sites
2 hours ago, ISE said:

Any word yet ? :(

 

on?

Share this post


Link to post
Share on other sites
1 hour ago, VITAS said:

on?

Never mind lol

Edited by ISE

Share this post


Link to post
Share on other sites

Hello Spacedock Team,

it seams there is an bug in the Apache config,

if I try to reach spacedock.info via www.spacedock.info i get an 503 - Service Unavailable.

 

Maybe you should redirect www.spacedock.info to spacedock.info in your apache.conf.

 

Something like this:

http://stackoverflow.com/questions/16200501/http-to-https-apache-redirection

NameVirtualHost *:80
<VirtualHost *:80>
   ServerName mysite.example.com
   DocumentRoot /usr/local/apache2/htdocs 
   Redirect permanent / https://mysite.example.com/
</VirtualHost>

<VirtualHost _default_:443>
   ServerName mysite.example.com
  DocumentRoot /usr/local/apache2/htdocs
  SSLEngine On
 # etc...
</VirtualHost>

 

Edited by FlatEric

Share this post


Link to post
Share on other sites
41 minutes ago, FlatEric said:

Hello Spacedock Team,

it seams there is an bug in the Apache config,

if I try to reach spacedock.info via www.spacedock.info i get an 503 - Service Unavailable.

 

Maybe you should redirect www.spacedock.info to spacedock.info in your apache.conf.

 

Something like this:

http://stackoverflow.com/questions/16200501/http-to-https-apache-redirection


NameVirtualHost *:80
<VirtualHost *:80>
   ServerName mysite.example.com
   DocumentRoot /usr/local/apache2/htdocs 
   Redirect permanent / https://mysite.example.com/
</VirtualHost>

<VirtualHost _default_:443>
   ServerName mysite.example.com
  DocumentRoot /usr/local/apache2/htdocs
  SSLEngine On
 # etc...
</VirtualHost>

 

Thats not the problem. The whole site is hit or miss at the moment, most likely because of the recent 1.2 release.

Share this post


Link to post
Share on other sites

I have been seeing the problem of, the "follow" button is missing. I get the "unfollow" option for mods followed, but can't add and follows.

Share this post


Link to post
Share on other sites

Seems to be down for me right now. I'm in AZ

Share this post


Link to post
Share on other sites
20 minutes ago, TiktaalikDreaming said:

From where?  Rough geographical location and ISP.  The site is distributed, so VITAS needs to have some idea which server.

Sadly, we lost our donated DO nodes some weeks ago, so the site is back on a single server

Share this post


Link to post
Share on other sites

Spacedock is terribly slow in Australia at the moment as well, also depends on what time you try to access it seems ok now but 3 hours ago it wouldnt even show a page. I am guessing its where the other TZ start to overlap and peak times cross the Aussie one we have crap internet most of the time, for a civilised country we have the worst internet.

 

Edited by Virtualgenius
  • Like 1

Share this post


Link to post
Share on other sites

The terribly slowness might be because the USA has been under a DDoS attack for the past day or so.

Share this post


Link to post
Share on other sites
1 hour ago, Ultimate Steve said:

The terribly slowness might be because the USA has been under a DDoS attack for the past day or so.

Those attacks have been on specific servers/websites, and I don't think the Russians/Chinese care anything about a mod site for a space game.  While I am aware that Amazon (which I believe is the web host for SpaceDock) was a victim of the attack, it shouldn't have any effect on their web hosting services, unless those servers were also targeted, which is entirely possible.

Share this post


Link to post
Share on other sites
1 hour ago, Ultimate Steve said:

The terribly slowness might be because the USA has been under a DDoS attack for the past day or so.

That DDoS attack is aimed at a DNS hosting provider, so if SpaceDock doesn't use that (spoiler: It doesn't), it's not affected.  There's a fairly good chance external referenced page components (aka images on imgur etc) can be affected.  They'll be affected for all users, it's dependent on where the content('s DNS) is hosted.  But the basic page should load if the only issue was the DDoS.

  • Like 1

Share this post


Link to post
Share on other sites

Attacks on DNS servers can effect anyone by way of who their ISP is using.

Share this post


Link to post
Share on other sites
On 10/23/2016 at 2:59 PM, Vorg said:

Attacks on DNS servers can effect anyone by way of who their ISP is using.

Yes and no.

Typically, the zone hosting DNS service is separate from client forward lookup servers.  That way, one can be purely internal facing and allow things like recursive lookups and caching.  What were hit were zone hosting services.

But, those zone hosting servers also had some root hints delegations, meaning all ISPs nearby would use them in the path for certain top level domain lookups.  I'm not sure which root hints they had.

Share this post


Link to post
Share on other sites

ddos traffic doesnt magicly apear at the target server. so its possible that interlinks between the sources and the targets will get saturated.

i had a spicke with a huge amount of non spacedock website related traffic (havaent looked at ckan traffic). The server got about double the traffic for a few days. I havent looked into the cause that deeply because it went away.

Im fairly certain that there isnt anything i could have done to make it better.

atm my hopes for me beeing able to afford a new server with a bit more reserves (the current one is running at its cpu limit nearly all the time)

Im also hoping for more helping hands in the development of the new codebase thats been in the work for half a year now. Theres mainly frontend stuff remaining (js/html/css) so if you want to help join us in our irc channel (see spacedock.infpo for infos)

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now