We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi. I'm in the process of setting up BudgetZero via docker with couchdb.
I have the docker image running for both and a reverse proxy running and reachable via my domain ie: https://budget.domain.com <---- reachable opens fine http://budget.domain.com:5984 <--- reachable opens fine
If I go to the docker local IP 10.10.0.7:8080, and set the sync url to http://admin:[email protected]:5984/budget it syncs with the couchdb database.
If I access BudgetZero via reserve proxy; https://budget.domain.com and set the sync url to the same as above: http://admin:[email protected]:5984/budget I get an error stating TypeError: NetworkError when attempting to fetch resource.
TypeError: NetworkError when attempting to fetch resource.
Let me know if I can provide anything to help.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi. I'm in the process of setting up BudgetZero via docker with couchdb.
I have the docker image running for both and a reverse proxy running and reachable via my domain ie:
https://budget.domain.com <---- reachable opens fine
http://budget.domain.com:5984 <--- reachable opens fine
If I go to the docker local IP 10.10.0.7:8080, and set the sync url to http://admin:[email protected]:5984/budget it syncs with the couchdb database.
If I access BudgetZero via reserve proxy; https://budget.domain.com and set the sync url to the same as above: http://admin:[email protected]:5984/budget I get an error stating
TypeError: NetworkError when attempting to fetch resource.
Let me know if I can provide anything to help.
The text was updated successfully, but these errors were encountered: