Error starting userland proxy: listen tcp4 0.0.0.0:8848: bind: address already in use
The problem with this error message is that the port is occupied
View occupied port commands
netstat -tanlp
Kill the process (note that instead of killing the port, it is the port of PID)
kill 6046
This is the current solution
To mention something else, it’s actually because uploading jar package failed to start Nacos, because Tomcat failed to start. Later, docker’s Nacos is used to solve the problem. The later results are appropriate and can be used. Docker is still good, ha ha
Read More:
- When docker starts tomcat, the access port of the container displays 404, and the source server fails to find the representation of the target resource or is unwilling to disclose an existing one
- Solution to the problem that listen TCP 0.0.0.0:3306: bind: address already in use port is occupied in Linux centos7
- The remote port occupation of Linux startup jar package script reports an error
- Failed to connect to 127.0.0.1 port 43571: problem solving record
- Through PID (process identification) to find the port (port) occupied applications, to solve the problem of port occupied
- Solution to the problem of failure to elect leaders when offline service is reported in Nacos
- Nacos starts in cluster mode and reports an error
- Docker starts the image and reports an error. Iptables failed: iptables — wait – t NAT – a docker – P TCP
- Record once the solution of gradle dependency problem: failed to determine a suitable driver class
- Record of solutions to internal error when VMware starts virtual machine
- Docker Nacos deployment uses container name to access 400 bad request
- NACOS error com.alibaba.nacos.api.exception.NacosException: failed to req API:/api//nacos/v1/ns/instance
- Docker starts MySQL container and reports an error driver failed programming external connectivity on endpoint mysq
- Port 4200 is already in use.Use ‘-port’ to specify a different port error Reasons
- filezilla Failed to create listen socket on port 21 for IPv4 solution
- The Tomcat connector configured to listen on port 8080 failed to start. The port may already be in u
- [Sovled] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
- Exception record. When eclipse starts, an error is reported when workspace is opened
- When the docker of win10 subsystem is started, the port is not available
- Solve the problem of Nacos double click flash back