-
Notifications
You must be signed in to change notification settings - Fork 193
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
[BUG] Can't connect to LNDHub in Firefox; works fine in Chrome #3005
Comments
@dienummer Can you verify that you can open Since it's exactly the same codebase for the firefox / chrome extension there could potentially also be a problem with resolving this local domain? Can you maybe follow the steps described in here and try to see if you find the root cause of this problem? Would be interesting to inspect both the network and console tab. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Describe the bug
In Firefox, when setting up Alby anew, it reports it cannot connect to local LAN instance of LNDHub (details below). I get one of two error messages. First, most common is
Connection failed. Is your LNDHub URI correct? API error (http://lndhub.local:3000):
. Secondarily I have seen :Error: API error (http://lndhub.local:3000):
(yes, there is a blank space after the final colon in both cases)However, it works fine in Chrome using the same connection string.
lndhub://<useridpart>:<token/pass-part>@http://lndhub.local:3000
Logs (bland):
Screenshots [optional]
Steps To Reproduce
Run LNDHub on LAN; hostname
lndhub.local
served by mDNS. serve directly on port 3000; no TLSSet up new wallet in BlueWallet. Copy connection string (
lndhub://...
)Load fresh instance of Alby in Firefox
Set password to get through
Select LNDHub
Paste connection string.
Fails with above error(s) in Firefox; Works fine in Chrome
Expected behavior
I expect it to connect correctly; or report an actionable error (rather than a blank string)
Alby information
Device information
Additional context
No response
Are you working on this?
No
The text was updated successfully, but these errors were encountered: