-
Notifications
You must be signed in to change notification settings - Fork 25
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
Unable to run bridge locally due to failed external requests (CORS) #1070
Comments
seeing the same here when running locally OSX, chrome, bridge-3.2.2, rainbow wallet so login always hits this was after trying to use the hosted bridge to initialize my network keys but it failing due to not supporting eip1559: so i figured maybe the hosted version was out of date and would try locally on latest |
@mikolajpp What commands are you using to run Bridge locally? Are you able to connect to the site using https? |
@sambarnes I also had issues with Rainbow when testing 3.2.2 locally. I ended up switching to another wallet (Trust) which worked as expected. Are you able to try another wallet? In the meantime, I filed an issue for the Rainbow team: |
I have the same issue. Firefox 115.4.0esr notably, the same setup but using the urbit.org bridge instead of the self-hosted one works, so I guess this is not due to the roller being offline. (edited) the opening screen is displayed, I choose to log in with Metamask, sign the message, then I get this error on the website:
the browser console is flooded with errors about not being able to reach Walletconnect, which I don't think affects me because I'm not using it. the errors that do seem relevant that appear after I click on the Metamask button are below:
what causes this? |
I was also having the same issue trying to setup Bridge 3.2.10. Though I was able to fix it, thanks in no small part to ~dinleb-rambep who pointed me to the right direction. I think the README is due for a little bit of an update since I have to scour the issue tracker for bits of info trying to get Bridge to run. I got the build commands from here.
This gave me a runnable .zip file that will actually load Bridge. But logging in with either the Master Ticket or Metamask gives me a "Unable to derive wallet from ticket" for the former and "{"code":7979,"data":{}}" for the latter. I was able to fix it by running a Python HTTPS webserver on localhost running at port 3000 with a self-signed cert. Here's the OpenSSL command and the Python script that I used to make it work:
Again, thanks to ~dinleb-rambep for the huge assist on getting this thing to work. |
Describe the bug
I followed the guide and installed latest version of bridge, running it locally. However, it does not work in firefox due to failed external requests.
As a result, the log in functionality does not work.
Desktop
The text was updated successfully, but these errors were encountered: