LycheeOrg / Lychee-v3

A great looking and easy-to-use photo-management-system you can run on your server, to manage and share photos.

Home Page:https://lycheeorg.github.io/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Getting blank screen when loading into website

EverlyScott opened this issue · comments

When I install and load into Lychee, I just get a blank screen
image

Log:

Error 001: Configuration not found. Please install Lychee first.

Diag:

Diagnostics
-----------
Error: Configuration not found. Please install Lychee for additional tests.

Chrome Version 77.0.3865.120 (Official Build) (64-bit),
Windows 10 Home x64 Version 10.0.18362 Build 18362

Still happens in incognito

I think I found out the issue, but I cant find out how to fix it...

When going into chrome inspector, the script tag is supposed to load dist/main.js, but in the sources tab, the file is not loaded.... in console it has no errors about it not being able to load the file.

and I can load the script in a web browser
image

Error 001: Configuration not found. Please install Lychee first.

This tells me that it cannot find the data/config.php file.

What install steps did you do so far ?

What install steps did you do so far ?

I completed all of the install steps multiple times

What were thoses ?

every thing on the installation wiki page

So you haven't fully installed Lychee yet. Basically you are missing the last step which is done online: the creation of the tables for the database.

Yup, but when I try to do that I just get that blank screen

And I'm guessing its because for some reason its not loading the /dist/main.js file.... and throws no errors in the chrome console

Rename the .htaccess into something else.

@d7415 can you ahve a look too ?

Also you can drop by our gitter: https://gitter.im/LycheeOrg/Lobby

Rename the .htaccess into something else.

hmm.... works

@ScribbleNerd Was there anything in your browser console with the .htaccess present?

Everything works now on a VPS.. I think the shared hosting was messing up something

The share hosting was probably having issues with the .htaccess yes. :(