Skip to content
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

mosquitto image with 1.6.10 unable to start websocket #1740

Closed
OkenKhuman opened this issue Jul 7, 2020 · 3 comments
Closed

mosquitto image with 1.6.10 unable to start websocket #1740

OkenKhuman opened this issue Jul 7, 2020 · 3 comments
Labels
Status: Completed Nothing further to be done with this issue, it can be closed by the requestor or committer.
Milestone

Comments

@OkenKhuman
Copy link

I use the below configuration

per_listener_settings true
persistence true
persistence_location /mosquitto/data/
log_dest file /mosquitto/log/mosquitto.log
persistence_file mosquitto.db
log_dest syslog
log_dest stdout
log_dest topic
log_type error
log_type warning
log_type notice
log_type information
connection_messages true
sys_interval 5
log_timestamp true
persistent_client_expiration 1m
listener 1893
protocol websockets
socket_domain ipv4
allow_anonymous false
password_file /mosquitto/config/more/client1.pass
max_connections 10
listener 1895
protocol websockets
socket_domain ipv4
allow_anonymous true
max_connections 10

but I got the following

mqtt_1   | 1594126251: mosquitto version 1.6.10 starting
mqtt_1   | 1594126251: Config loaded from /mosquitto/config/mosquitto.conf.
mqtt_1   | 1594126251: Opening websockets listen socket on port 1893.
mqtt_1   | 1594126251: Opening websockets listen socket on port 1895.
mqtt_1   | 1594126251: Error: Unable to start any listening sockets, exiting.

please help me out

@chapin666
Copy link

me too.

@dommar04
Copy link

We encountered the same problem after updating to verison 1.6.10. mqtt protocoll worked but with websockets it simple did not start anymore. (Centos7)

Is the reason for this problem alreay known? Any known workarounds?

@ralight
Copy link
Contributor

ralight commented Jul 14, 2020

The workaround is to define a non-websockets listener. This is now fixed in the fixes branch.

ralight added a commit that referenced this issue Jul 14, 2020
@ralight ralight added the Status: Completed Nothing further to be done with this issue, it can be closed by the requestor or committer. label Jul 15, 2020
@ralight ralight added this to the 1.6.11 milestone Jul 16, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 11, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Status: Completed Nothing further to be done with this issue, it can be closed by the requestor or committer.
Projects
None yet
Development

No branches or pull requests

4 participants