moved to new host, since then random time-out errors
By Petra Sood on Monday, 17 April 2017
Posted in Technical Issues
Replies 19
Likes 0
Views 321
Votes 0
Dear team easyblog and forum users.

We moved our whole webiste to a new host and their server.
There is Joomla and EasyBlog on the main website and an Oxid eShop on a subdomain.
Since then we have user-realted errors that appear randomly by clicking somewhere in the blog (frontend) or working in the backend. The error also can be reproduced by clicking on special categories* or by clicking on an article via tagcloud for example.
*We made an joomla menue for that instead of using the navbar. But we tested taking it off but it made no difference.

The user gets a timeout error message on the mainsite and the subsite and it takes roundabout 10-15 minutes until you can reach any site again. Cause the shop is also affected and it shows in the ordering rate, we completely took easyblog down and removed all the links guarding to the blog.

Because we were also working on the blog settings and article in the same week as we got moved our website, we cannot really tell if we made a mistake or if it's something to do with the new server.

So are there any ideas, what is causing the problem?
We were so happy with the blogging tool and really appreciate to get it working again!

Thanks in advance and we hope you enjoy your day – team kulmine
You're welcome.

We just released Easyblog 5.1 today, you can consider to update from 5.x to 5.1.2.
Arlex Wong
·
Wednesday, 19 April 2017 19:48
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Petra,

Hm, to be honest with you, it's really difficult for me to tell what went wrong but EasyBlog should never act so problematic when you are moving a host. I believe there could be some conflicts with the plugins that is running but to be honest, I am just guessing here unless I have a real look into the issue.

Would it be possible for you to setup a staging / test site so that we could look into this?
Mark
·
Monday, 17 April 2017 22:09
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Mark,
thanks for replying that fast.
I'm no programmer or anything so I don't know how to set up a staging or test site. I'll talk it over with our expert.
We also will ask our host team to look into the error logs on the server, maybe they can tell something.

We also tested:
- shutting down all easyblog modules inspite of the main module … made no difference.
- when having the timeout error, we reconnected to the internet with a new IP-adress – site was availabla at once then (until next error)

I'll keep you updated.
Kind regards
Petra Sood
·
Monday, 17 April 2017 22:59
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Petra,

Hm, if you have already turned off all modules and EasyBlog and it's still hitting timeout errors, I believe it really isn't an EasyBlog issue but I am just speculating here because it's very hard for me to tell what went wrong.

It would be ideal if your team could setup a staging site and / or if your web host could provide you with some sort of logs so that we can determine the bottlenecks.
Mark
·
Monday, 17 April 2017 23:37
·
0 Likes
·
0 Votes
·
0 Comments
·
Hallo Mark.

When Easyblog is completely turned off, the timeout doesn't occur any more!
But we tried turning off all modules but the one „easblog“ module itself and the timeout occured.
So from our perspective it has to do with easyblog.

Strangely the host team doesn't have any problems like it, even on the mobile.
They checked the logs but have no idea about it.
edit: Ive attached it as txt
(I see "apple" mentioned often in the log – but the timeout occurs as well on mac, pc, several browsers and android mobile)

Since I don't know how to put up a test site … I've seen in other posts that you asked for ftp- and joomla-accounts.
Would that help to give them to you?
edit: I entered the data into the Site Details sheet.
Petra Sood
·
Tuesday, 18 April 2017 18:17
·
0 Likes
·
0 Votes
·
0 Comments
·
hey there,

Can you check my attached screenshot is it this is what you mean the time out error?

If yes, I realised your FTP directory folder got this kind of .htaccess file, may i know these following .htaccess file is it suppose to located at following directory folder?

/components/.htaccess
/plugins/.htaccess
/modules/.htaccess
/administrator/components/.htaccess
/libraries/.htaccess
/logs/.htaccess
/includes/.htaccess
/images/.htaccess
/cli/.htaccess
/tmp/.htaccess
/media/.htaccess
/administrator/cache/.htaccess
/administrator/help/.htaccess
/administrator/language/.htaccess
/administrator/manifests/.htaccess
/administrator/modules/.htaccess
/administrator/templates/.htaccess

Currently I still don't have any ideas yet why it hitting timeout error, I've temporary renamed these .htaccess file to .htaccess_bak , can I have the permission to uninstall Easyblog from your backend then reinstall again? Doing this uninstall and reinstall process will not touch your existing blog post data from your database.
Arlex Wong
·
Tuesday, 18 April 2017 20:16
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Arlex
Thanks for taking a look! Your support is excellent and quick, great work you are doing. This feels good.

The blog is working now well (just some few links I have to renew).
I don't know if the credit goes to you or our programmer who did set up the joomla for us …
He deactivated and reactivated the module manager – the logentries gave him that hint, he said.

The timeout message we got seems to have been the same as your screenshot "unable to connect" – only in German.

But maybe your intervention helped as well!
So is it still a useful step in general to reinstall easyblog?
Would this delete our CSS-changes in the design? This would be hard to lose all the work we did put into.

We are happy we can use this powerful tool again!
Best wishes – team Kulmine
Petra Sood
·
Wednesday, 19 April 2017 01:24
·
0 Likes
·
0 Votes
·
0 Comments
·
You are welcome Petra

So is it still a useful step in general to reinstall easyblog?
Would this delete our CSS-changes in the design? This would be hard to lose all the work we did put into.

If your programmer add those custom css in Easyblog core file, then that will lose all your previous work if reinstall Easyblog from your site. Perhaps you can consult with your programmer and see which file their add those custom css into?

By the way, actually I am not really sure is it because of these .htaccess file causing that timeout issue, because based on what i see those .htaccess file code, it seems like it shouldn't cause this timeout error.
Arlex Wong
·
Wednesday, 19 April 2017 10:19
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Arlex,

good. I'll talk it over with the programmer.

The problem is solved – but I'd like to let this thread open as „not answered“ because of that idea to reinstall easyblog.

Til later, have a nice day! :-)
Petra Sood
·
Wednesday, 19 April 2017 19:26
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Arlex,
We agreed on going on with our actual setting now, because it is working. If they may occur any similar problems agein we will consiger to reinstall it.

Thanks and kind regards.
Petra Sood
·
Wednesday, 19 April 2017 21:55
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for updating Petra, glad that your issues are resolved now.
Mark
·
Wednesday, 19 April 2017 22:03
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post