getmusicbee.com
General => General Discussions => Topic started by: Steven on February 24, 2018, 09:07:43 AM
-
A couple of days ago the host for the getmusicbee.com website upgraded the OS version. Unfortunately the SSL certificate was messed up and additionally a script incompatibility took the site down. Thats now fixed.
But there is still an ongoing issue where you will occassionally see a "500 Internal Error".
It has been reported but so far the solution they provided hasn't worked
-
Thank you Steven for keeping us up to date on the situation.
-
I put a notice up on the wiki, directing people to Twitter if they're unable to access the website. Hope it gets resolved!
-
FYI, as of now I have stopped getting the "500 Internal Error" messages that were the norm earlier today, hopefully that means the fix is in!
-
FYI, as of now I have stopped getting the "500 Internal Error" messages that were the norm earlier today, hopefully that means the fix is in!
As for now the site is using cloudflare for cache CDN. But there are new problems, some pages do not work. forum seems intact though. so thats a good sign.
Hopefully we will have a working solution in few days or so.
-
Apparantly it can take up to 2 days for the cloudfare configuration to propogate, and hence some people will experience SSL secure connection failures. I've experienced this a few times myself but eventually get through
-
All the issues with cloudfare should now be resolved.
While the "500 Internal Error" issue has much improved, I am finding it still happens sometimes. In the next month or so, AvikB is planning to make a change that should help further.
-
I'm seeing a lot of error messages when browsing the forum, not very usable at the moment.
-
I'm seeing a lot of error messages when browsing the forum, not very usable at the moment.
What type of error messages?
-
i very very very frequently see '500 internal error' message. but refreshing a page always helps.
-
Yeah, I'm still getting the Internal Server Error message fairly often. There will be long spells without it, and then it shows up again. (Appropriately, even when I posted this message!)
-
Yeah, I'm still getting the Internal Server Error message fairly often. There will be long spells without it, and then it shows up again. (Appropriately, even when I posted this message!)
Yes, me too. Especially today more than yesterday. But as boroda74 said, a refresh clears it. Still ... it shouldn't be.
-
Yeah, I'm still getting the Internal Server Error message fairly often. There will be long spells without it, and then it shows up again. (Appropriately, even when I posted this message!)
Yes, me too. Especially today more than yesterday. But as boroda74 said, a refresh clears it. Still ... it shouldn't be.
The new Hosting server OS update seems to broke some stuff along with this annoyance.
I am working on a major update for the website backend, specially caching that should reduce server resource usage. Hopefully this might solve it.
According to Steven this problem started with SMF 2.0, before the new website was even introduced. There was a temporary fix for this back then, but with the new server update it is not compatible anymore.
I am looking into it, will let you guys know if a proper fix is possible or not.
-
actually i haven't seen any error today at all.
-
actually i haven't seen any error today at all.
Still seeing the error, but not as often :-X
-
Just now I tried to sign out several times, but I can't.
-
Just now I tried to sign out several times, but I can't.
it should be fixed now
-
Yep. Thanks!
-
As an experiment, i am making use of cloudfare's "cache everything" feature on the add-ons page to see if it helps with the website issues.
One side-effect will be that any new skins/plugins or updates might not show for up to 4 hours.
-
Internal server (500) errors are back today.
Also clicking on links sometimes result in a blank page, which may simply be the 500 but not displaying the error.
-
i can confirm that i haven't seen 500 errors today.
-
These errors have not fully gone away, but i dont see them very often in the error log.
I dont see the situation changing until the next set of website changes AvikB is making is released. Even then they might not fully go away
-
These errors have not fully gone away, but i dont see them very often in the error log.
I dont see the situation changing until the next set of website changes AvikB is making is released. Even then they might not fully go away
I see the 500 error at least one time a day. This morning was much more frequent, hence the post.
Thanks for the update, Steven.
-
i updated the PHP version to 7 this morning and cant see any "500" errors so hopefully that change enough to solve this issue
-
Perhaps the PHP update is why I haven't seen a single 500 error today. I'll let you know if otherwise. Thanks.
-
Just had a 500 error after not seeing one since Steven's last post in this thread.
-
Just had a 500 error after not seeing one since Steven's last post in this thread.
Yes, same thing. Twice this morning.
-
now i frequently see 522 errors. also site became very slow.
-
Seeing more 500 errors today. Three in the course of ten minutes.
-
The forum is still not opening to new, unread posts when I hit the site using
https://getmusicbee.com/forum/?action=unread
I never log out of the forum unless I'm using a different browser or computer. This is what showed this morning:
(http://i.imgur.com/a5RMb1El.jpg) (https://i.imgur.com/a5RMb1E.jpg)
I then went to the forum home page and saw this, which as you know, indicates new, unread messages:
(http://i.imgur.com/idPwJfAl.jpg) (https://i.imgur.com/idPwJfA.jpg)
Lastly, I have to click on one of the 'unread' sub-forums and look for the 'new' icon and finally get to see the new, unread posts.
(http://i.imgur.com/dEcWGEYl.jpg) (https://i.imgur.com/dEcWGEY.jpg)
If the new, unread posts link would work as before, all new, unread posts are on one page and is much easier to navigate. This has been going on since the 500 errors started, but I can't see how it's related. It's not browser related as it happens with Waterfox, Firefox, Chrome, and IE.
-
In addition to the forum loading links very slowly today, I've seen five 500 internal server errors in less than ten minutes.
-
Yes i have seen a few as well. Unforunately i think what has happened is when the web hosting provider moved musicbee to a new server, they reduced the memory allocation for PHP - probably in order to squeeze more sites onto the one shared server (I dont know this for a fact but it I think its very plausible based on what I know).
When the site runs slow, often i see a spike on cloudfare for invalid requests.
Apart from the planned change AvikB will do for the addons page, I dont think there is much more that can be done short of getting a dedicated web server which is very expensive.
If anyone reading this is a server administrator or knowledgeable about web hosting i would be interested in any comments.
-
i think what has happened is when the web hosting provider moved musicbee to a new server, they reduced the memory allocation for PHP - probably in order to squeeze more sites onto the one shared server (I dont know this for a fact but it I think its very plausible based on what I know).
While not a server admin, I did spend more years than I care to think about in IT managing a 300+ user network. What you say does indeed sound plausible. Unfortunately.
I dont think there is much more that can be done short of getting a dedicated web server which is very expensive.
I think a dedicated server should not even be considered. I certainly don't want to see an increase in your expenses. And crowd-funding might work at the start, but the funding is not likely to be sustained after the initial push. So I'm content to live with it as is. Would you like me to continue reporting the 500s, or just let it go?
-
Would you like me to continue reporting the 500s, or just let it go?
Probably not needed until AvikB has made the next version available
-
Yes i have seen a few as well. Unforunately i think what has happened is when the web hosting provider moved musicbee to a new server, they reduced the memory allocation for PHP - probably in order to squeeze more sites onto the one shared server (I dont know this for a fact but it I think its very plausible based on what I know). When the site runs slow, often i see a spike on cloudfare for invalid requests. Apart from the planned change AvikB will do for the addons page, I dont think there is much more that can be done short of getting a dedicated web server which is very expensive. If anyone reading this is a server administrator or knowledgeable about web hosting i would be interested in any comments.
Yeah i am also suspecting the same.
Honestly at this point the issue might persist even with the new update. Couldflare should've solved the caching issue, but since it hasn't..... i don't think any caching implementation would help.
In the long run maybe switching to a new hosting provider will solve this problem.
-
Edit: All good now. Submitted an add-on earlier but it wasn't published to the add-ons page until a long while later, even though I could view it from a direct link.
-
there is a 4 hour caching rule on the main add-ones page in place with cloudfare to help with the "500 Internal Errors" ie. you wont see new submissions straight away
-
there is a 4 hour caching rule on the main add-ones page in place with cloudfare to help with the "500 Internal Errors" ie. you wont see new submissions straight away
Ok, that would explain it. Maybe AvikB could add a notification during the add-on submission process, to avoid confusion.
-
there is a 4 hour caching rule on the main add-ones page in place with cloudfare to help with the "500 Internal Errors" ie. you wont see new submissions straight away
Ok, that would explain it. Maybe AvikB could add a notification during the add-on submission process, to avoid confusion.
You need to wait until the next version of the website releases. I didn't got any chance to work on the new site for the past 2 week. Hopefully i will get some time this week.
I will probably add the notification if the site still needs cloudflare caching after the new update.