Verifica log server e posta il fatal se lo trovi

Can you try the SCORM on other Chrome instances? Other devices, o.s., and so on? Does the issue always occur?

Hi,
you should inspect your console developer window, first, and report errors, if any.
Alongside with front end errors, you should analyse backend errors too.

Yes, but va/pt results are reserved.

You'd better study how Apache works before publishing sites, otherwise you'll encounter errors or (even worst) security problems. Never make root own published folder, privilege escalation attack would be easy
apachectl -S, which will show something Apache user and group

Check that Apache user has write permission on that folder

Just replied to the other topic.

Check Apache error log. You'll find a fatal error.

So you can solve, can't you?

Hi,
unfortunately mysql has not a verbose error logging, so one should be on your instance to investigate further.
One question: what about sql_mode configuration parameter and collation type/character set of your db?