Stuck on loading, please wait

Submitted by TheImpactAlliance on Tue, 11/17/2020 - 07:18
Forums: 
Content creation

Hi, I have installed my H5P on a Bluehost server (Wordpress). When I add new conten on my desktop  for most activities it says that it is installed but then gets stuck on "loading, please wait..." Only the accordion works. I have tried it on Chrome, Safari and Firefox.  I am using the latest version of h5p. I don't seem to have any php errors but I do have some console errors. I have deactivated all my other plugins.

Please help!

Greetings,

Sven

 

 

Attachments: 
Image icon error.png
Image icon Screenshot 2020-11-17 at 06.57.22.png
Summary: 
Add new, stuck on loading, please wait...
Content types: 
all content types
otacke's picture

otacke

Tue, 11/17/2020 - 18:40

Hi TheImpactAlliance!

That 403 message indicates that the server process doesn't have the rights to access the files that it requires. Please make sure that you didn't accidentally changed the file permission settings, e.g. by installing manually or by configuring some .htaccess in a way that prevents accessing those files.

Best,
Oliver

TheImpactAlliance

Wed, 11/18/2020 - 08:17

Hi Oliver, 

Thank you so much for that info...could you just help me out and be a wee bit more specific. I would be eternally (or up to a year :P) grateful!

 

Sven

otacke's picture

otacke

Wed, 11/18/2020 - 08:57

Hi Sven!

I am sorry, I am not sure how I could be more specific without duplicating virtually any tutorial that a search for e.g. "403 .htaccess" would yield. It's not specific to H5P.

Some basic background maybe: Your server replied with an HTTP response code of 403. That means the server cannot access those files.

One reason could be file access rights that can be set on the files. For example, someone could have tried to install H5P manually by copying the files to the server as user x, but the files need to be own by the server process (usually named daemon or www-data) or be assigned to a group that the server process can access or no restrictions should be set at all (the latter is not a good idea).

Another reason could be setting similar restrictions not on the file system level, but on the server level by setting special access rules. Those are intended to prevent users from snooping around on the server. Those restrictions are often set in files named .htaccess and can be tricky to define and can collide with rules for forwarding etc. Someone would have to check these.

There could be other reasons, too, but those are the most likely ones.

Best,

Oliver 

TheImpactAlliance

Wed, 11/18/2020 - 10:48

Thanks so much Olivier!