Hi,
I didn't want to make an "issue" of this since I suspect it is user error but if you'd prefer, I can do that.
I am trying to set up ArchiveBox with Docker behind a Caddy Reverse proxy. I did make a few minor modifications to the docker-compose file to (a) use port 25005 (which is what I have in Caddy proxying to Archive Box), (b) set a full path to my data folder, and (c) settings.
My docker-file.yaml looks like: (where my username is USER
version: '3.7'
services:
archivebox:
# build: .
image: ${DOCKER_IMAGE:-archivebox/archivebox:latest}
command: server 0.0.0.0:8000
stdin_open: true
tty: true
ports:
- 25005:8000
environment:
# Terminal
- USE_COLOR=True
- SHOW_PROGRESS=False
# Other
- CHECK_SSL_VALIDITY=False
- TIME_ZONE='US/Mountain'
# Privacy
- SUBMIT_ARCHIVE_DOT_ORG=False
- PUBLIC_INDEX=True
- PUBLIC_SNAPSHOTS=True
# What to save
- SAVE_WARC=False
volumes:
- /home/USER/serve/archivebox:/data
And I set the directory:
$ mkdir -p /home/USER/serve/archivebox/
$ chmod 777 /home/USER/serve/archivebox/
Then, in the directory of the yaml file, I run:
$ docker-compose run archivebox init
$ docker-compose run archivebox manage createsuperuser
(follow the prompts)
then finally:
$ docker-compose run archivebox server --debug
I added --debug
since I cannot seem to get any usable info.
So anyway, I get nothing when I go to the site! I see no output on in the window and I am not seeing anything in the browser.
I though maybe it was my Caddy config but (a) this is the identical one I use for other working apps (docker and otherwise) and (b), I tested with elinks going to 127.0.0.1:25005 but that too doesn't work.
Any ideas?