-
Notifications
You must be signed in to change notification settings - Fork 28
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
Pairing does not work #96
Comments
Fixed this a few minutes later -- instead of using the subdomain as the base URL, I gave it the container's interface IP |
but this IP did not work. I am also running it on docker through nginx. Thanks |
@BitizenOne Are you able to load the web UI through that IP? That's all I did |
@yapishu no, the IP doesn't seem to work. I am able to access the IP on the host through curl, which is a headless ubuntu, but cannot use that IP for access from the internet. I am running nginx in a container as well as btcpay. I assume you were running nginx on your host machine without docker and running btcpay through docker? I'm still digging on how to solve this issue. Thanks for the reply |
@BitizenOne so you're trying to connect Transmuter from a different device across the internet? If Btcpay and Transmuter are on the same host they should be able to talk via the local interface. If they're on separate devices, you will need to expose the port or configure a reverse proxy that forwards to Transmuter's local IP. I was running all three (btcpay/transmuter/nginx) on the same host using the standard Docker setup. I had HTTPS disabled on nginx and used a separate reverse proxy with HTTPS outside of my docker setup to expose it to the internet. |
For the record: |
Thanks, I could resolve the issue in this way. It feels unsafe though to not beeing able to use SSL. First grab the IP and Port of the BTCPayServer Container: Then enter as Server Host: |
Hello,
I've run into an issue setting up Transmuter with my instance. Everything else seems to be working fine, but when I try to pair it, I get an error about it not being able to establish a connection.
I am using the Docker setup, following the instructions from the primary documentation. I haven't done anything unusual, except that my BTCPay server subdomain is served with https via a reverse proxy on the edge of my network, and https is disabled on the docker instance itself. Not sure if that's relevant, but it's the only place I really diverged from an otherwise vanilla setup.
Thank you for any help you can provide
The text was updated successfully, but these errors were encountered: