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
Docker install does not work on Ubuntu 20.04 #263
Comments
Hi! Could you post full list of settings you have used? That's basically: cat .env # execute in bitcart-docker dir
cat /etc/profile.d/bitcartcc-env.sh Please redact any sensitive settings if needed. That error may often occur when https is not enabled, i.e. BITCART_REVERSEPROXY != nginx-https docker logs compose_backend_1
docker logs compose_admin_1
docker logs letsencrypt-nginx-proxy-companion |
Ok now we're narrowing it down... LetsEncrypt issues. What should i be setting in env for it? root@crypto1:/home/jd/bitcart-docker# docker logs letsencrypt-nginx-proxy-companion |
Ok, resolved that with setting: BITCART_LETSENCRYPT_EMAIL Now it's hanging on something else, let me see what I find. |
Weird, did you have it set? It shouldn't be required anyway |
Ohh, I can reproduce on a new deployment. It is a regression due to unpinned image upgrading to 2.0.0: |
It is also grabbing a new cert every restart it seems like. [Sun Feb 6 19:47:49 UTC 2022] Create new order error. Le_OrderFinalize not found. { |
A workaround for now would be: ./stop.sh
docker image rm jrcs/letsencrypt-nginx-proxy-companion
docker pull jrcs/letsencrypt-nginx-proxy-companion:v1.13.1
./start.sh Looks like so, it doesn't mount the new volume dir. |
Fixed by bitcart/bitcart-docker@7f9e90e You can now do As per the rate limits, probably waiting a bit should help Let me know when the issue is fixed so that we can close the issue |
Still having issues - ssl seems to work correctly but now things just hang when i try to visit the HOST. After 60 seconds a page pops up saying admin is unconfigured with an error. { "message": "Client network socket disconnected before secure TLS connection was established", "name": "Error", "stack": "Error: Client network socket disconnected before secure TLS connection was established\n at connResetException (internal/errors.js:639:14)\n at TLSSocket.onConnectEnd (_tls_wrap.js:1570:19)\n at TLSSocket.emit (events.js:412:35) I'm setting: export BITCART_REVERSEPROXY=nginx-https It's not showing up in .env after running setup but does show up in "variables passed" root@crypto1:/home/jd/bitcart-docker# cat .env Logs don't show anything unusual... not sure what i missed, i'll try again soon. |
Well I see some issues with your setup, both store and admin host share same URLs unset BITCART_STORE_HOST
unset BITCART_ADMIN_HOST
unset BITCART_STORE_API_URL
unset BITCART_ADMIN_API_URL
./setup.sh That will enable one-domain mode, so you will access the store at https://crypto-1.mynetwork.net, the admin at https://crypto-1.mynetwork.net/admin and api at https://crypto-1.mynetwork.net/api See https://docs.bitcartcc.com/guides/one-domain-mode P.S. That's why I always ask for config first, users are often mistaken with the domain settings. Do you know how could we clarify this more? |
Ok that worked. thank you sir. I followed this doc, it might need updating. "Why was it done like so? It's because it is possible to run Merchants API on one server, and everything else on different servers. if https (BITCART_REVERSEPROXY=nginx-https, default)export BITCART_ADMIN_API_URL=https://$BITCART_HOST if http (BITCART_REVERSEPROXY=nginx, local deployments, other)export BITCART_ADMIN_API_URL=http://$BITCART_HOST |
Well it's a description of another posible usecase (onedomain mode off), but right at the top of the page it says:
|
Closing as the issue was resolved, I will look if there is something I can do with the docs |
I tried multiple install settings, several rebuilds. It all starts fine, trying to connect via HTTPS gives a 500 Internal server error. .. one time I got an API error instead. Nothing I tried worked. Any magic I'm missing?
The text was updated successfully, but these errors were encountered: