Port NaN already occupied. Using port 41663 instead.
See original GitHub issueHi,
It seems like sqlpad is choosing arbitrary port numbers instead of 3000.
Here is my docker file:
FROM sqlpad/sqlpad:5.6.0
ENV SQLPAD_ADMIN "admin"
ENV SQLPAD_ADMIN_PASSWORD "admin"
ENV SQLPAD_PORT 3000
When starting it throws the following message:
Port NaN already occupied. Using port 41663 instead. Welcome to SQLPad! Visit http://localhost:41663 to get started
Why is this happening? How can I force it to connect to the port I want? Thank you
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:11
Top Results From Across the Web
Port 5001 is not open on localhost, could not start Functions ...
Any idea :/? ⚠ functions: Port NaN is not open on localhost, could not start Functions Emulator. ⚠ functions: To select a different...
Read more >Firebase serve error: Port 5000 is not open. Could not start ...
I'm using Windows 10, so I've tried to change the port number, check if the port is blocked by Firewall and I create...
Read more >Untitled
Laserjet m1212nf mfp ink, Dr shearer florence kentucky, Ibilex 500 uses, ... Abdulla rashim gizaw 3, Dlink switch 8 port, Ksi reacts to...
Read more >RARLAB WinRAR < 5.70 Beta 1 Multiple Vulnerabilities
The version of RARLAB WinRAR installed on the remote Windows host is prior to 5.70 Beta 1. It is, therefore, affected by the...
Read more >FEDERAL REGISTER - GovInfo
Rockwell Corp. Applies to Aero Com mander Model 1121 series airplanes, S/N. 3 through 150. Compliance required as Indicated unless already accomplished.
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 Free
Top 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
The choosing of a random port is the result of the port check.
Maybe a better way of putting it – the library used to detect the port is failing at handling a URI, as I believe it expects a number or string that contains a number.
https://www.npmjs.com/package/detect-port
Version 5.8.4 has a fix to always treat port as a number. Docker hub is still building it. Should hopefully help add clarity to the log message.
Another helpful means of troubleshooting would be to set the app log level to debug with
SQLPAD_APP_LOG_LEVEL = debug
. All config values will be logged when doing so.