-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
localhost:8080 after installation unavailable #18
Comments
Hi nautilus1905, what do you mean by shows nothing? |
H hoehnp, thanks for responding. |
Hi @nautilus1905, I will test next week on my installation and report back. At this point |
Thank you very much! |
Any news about the "localhost:8080" issue? |
I just tested again. I also get an empty page. And I think this was how it always was. I would only check if a zotero client can connect successfully. |
Hi, |
Hi, |
Hi, |
I will try to re-build the docker image with the #5 issue (using the IP instead of 'localhost') |
Hi, I have some progress to report. |
Hi @nautilus1905, i think there is a small misunderstanding. Generally, I don't think there should be anything visible in the browser. If you also want a web interface you can have a look on the fork Christian Nils. He added weblibrary which could be what you want. |
Ok, thank you for your help. |
Hello I tried this version but the web-library just show a z letter in the middle page of "localhost:8084" and cannot use it. |
Hi @MohamedElashri, |
Hello @hoehnp Thank you for reply. there is not issue tap in his repo to ask questions. anyway I came to the answer from him at client's repo here where he answered my question. |
@MohamedElashri |
Hi @nautilus1905 @MohamedElashri |
Hello,
I tried several times to build up a docker installation on a linux ubuntu 18.04, later on an antix 19.2 (debian buster derivate).
Every time I have the same problem. While the localhost:8082 and localhost:8083 work,
the localhost:8080 shows nothing.
Attached is the log of the the execution of run.sh
zotero-prime.log
The text was updated successfully, but these errors were encountered: