The Service Seems Down - Githubissues

hyperobject / crossorigin.me

A CORS proxy for everyone.

http://crossorigin.me

MIT License

679 stars 132 forks source link

The Service Seems Down #41

Closed kutec closed 8 years ago

kutec commented 8 years ago

Hi I am trying to implement the functionality where I need to fix crossorigin issue. I found crossorigin.me useful in this category. But the site is giving below error.

Error 522 Ray ID: 2938b7d5a0fb2ddf • 2016-04-14 17:01:24 UTC Connection timed out

Could you please intimate? Also share the up time so that I can make a decision whether to consider for app or not.

Thanks.

christophwolff commented 8 years ago

demobox commented 8 years ago

Also down from 213.139.137.6 :-(

hyperobject commented 8 years ago

Thanks for letting me know. Looks like there's some kind of memory leak in the code, which is making the DO droplet crash. Working on fixing it, but there's probably going to be quite a bit of downtime in the next few days as I try and fix the problem.

I'll be posting progress updates on @corsproxy and @technoboyIO on twitter.

hyperobject commented 8 years ago

Should be far more stable now. Going to create a new issue about the memory issue.

demobox commented 8 years ago

Working on fixing it

Many thanks for taking a look at this, @technoboy10!

demobox commented 8 years ago

@technoboy10 Service seems to be down again..? :-(

kutec commented 8 years ago

Still down for me :(

hyperobject commented 8 years ago

Still dealing with memory leaks. 😞

@demobox @kutec Should be back up, I bumped up the available RAM on digital ocean so the memory leak shouldn't cause as much trouble hopefully. (Which, of course, means everything will be on fire in another 12 hours :P)

demobox commented 8 years ago

Still dealing with memory leak

Thanks for the update...good luck, and many thanks for continuing to taking a look at this!

schme16 commented 8 years ago

@technoboy10: silly question, but are you settings the environmental variable NODE_ENV to 'production'? I've had all sorts of weird memory leaks with the http/https modules when I've forgotten to set it.

Also figure I should reference these issues together: #40 #42

hyperobject commented 8 years ago

@schme16 The sillier thing is that you're right - I totally forgot to do that! Thanks for the help. :D

schme16 commented 8 years ago

@technoboy10: Haha, I just hope that it turns out to be something so simple! Occasionally I've had to do manual garbage collection by starting the node process with the --always-compact --max_old_space_size=60 --nouse-idle-notification --expose-gc flags and calling global.gc(); in a setTimeout set for 5 minutes (or whatever)- but it's a yucky road to have to go down...