How to get rid of `localhost:3000` in the address bar
See original GitHub issueThere was a discussion about how to get rid of the localhost:3000
in the browser address bar in Slack and what to do about the port number.
When mapping blockstack-portal
to (for example) 127.1.2.3
you can let bind the portal to 127.1.2.3:<port>
and use any port you’d like to use (even port 80 which means no port in browsers). The only thing that could interrupt are programs which bind to a port on all network interfaces.
I hope I didn’t miss anything there^^
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Getting rid of "localhost:3000" URLs · Issue #34 - GitHub
Using the obvious solution of making the URLs relative (e.g. '/api/users/' + username has a subtle issue. It seems to work, when moving...
Read more >Getting rid of localhost:3000 URLs for ReactAsync
To start, use a simple plugin function for superagent. This rewrites absolute urls - but only on the server. This means that the...
Read more >how to remove "localhost:3000" in email notification - Redmine
1. Click on Adminstration in the topmost bar. 2. Click on Settings on the new page. 3. Click on the general tab. 4 ......
Read more >Localhost Refused to Connect Error: 5 Confirmed Ways to Fix It
Enter chrome://net-internals/#hsts on your browser's address bar. Chrome's HSTS settings. Locate Delete domain security policies, then type ...
Read more >How to access localhost: 3000 - Quora
To access it, open your web browser and type "localhost:3000" into the address bar. This will take you to the home page of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Moving to native app #599 will solve this.
Closing as stale. So long as this runs in a browser, it’s going to be this way. If we move to another form factor, this will be addressed as a part of that effort.