-
Notifications
You must be signed in to change notification settings - Fork 11
Can't use host:port/path on Caddyfile #21
Comments
@aigooman hey! Sorry to hear that. Just to make sure: the path to the database file you indicate doesn't exist right? If it's from Just tried the following Caddyfile (similar to yours):
And had no problem at all. If deleting the DB doesn't work, please let me know and also take a screenshot at Network tab |
caddy
Can't open index and login |
It works! Thank you for your help! |
It seems that you have to indicate the port 80 to run http.filebrowser. |
@aigooman can't reproduce that issue. If you don't set a port it is supposed to default to 80 as far as I know. Anyways, File Browser doesn't use the port for any port of the code so I don't really know why you are having issues. |
@hacdias If I use my.url directly, it will use https and it won't redirect to my.url/login?redirect=%2Ffiles%2F to show the login index, but when i set port 80 and set tls to be off,it runs well. |
Hmm... I will take a look at both your issues then 😄 |
Thanks~ |
I use filebrowser as caddy's plugin http.filebrower. My caddyfile is:
Then I run caddy with no error. But when I enter the url, the index is blank, there is no login web. However, I can still enter https://my.url/files to see my file. Did I do something wrong?
When I enter https://my.url , chrome shows:
The text was updated successfully, but these errors were encountered: