-
Notifications
You must be signed in to change notification settings - Fork 168
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
UpnpListener encountered an error. Shutting down #110
Comments
As you can see
My startup line:
If you really need to change the port, consider changes in
Best regards, |
I tried again and made sure I used a port that's not in use (as earlier btw). Response was:
Same bind error, but all these ports are free... |
Did you confirm with:
lsof -i -P -n | grep LISTEN
or
netstat -anp tcp | grep LISTEN
… On Sep 23, 2019, at 3:43 PM, mcwieger ***@***.***> wrote:
I tried again and made sure I used a port that's not in use (as earlier btw). Response was:
Tomcat initialized with port(s): 8086 (http) 8081 (http) 8082 (http)
Same bind error, but all these ports are free...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#110?email_source=notifications&email_token=ABLDPSFLJIH6DVHSJ2JKC7LQLEL6HA5CNFSM4IT6U3N2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7MBB2A#issuecomment-534253800>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABLDPSB4NCBJZRWC7EGV4FLQLEL6HANCNFSM4IT6U3NQ>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm trying to use Amazon Echo HA Bridge as an alternative to the regular HA Bridge, as I only use it for Echo and it recently started to act up.
I'm on a Synology DS414 (no Docker). I'm trying to start it with:
/volume1/@appstore/Java8/j2sdk-image/bin/java -jar /volume1/web/aehab/amazon-echo-bridge-0.4.0.jar --upnp.config.address=192.168.2.201 --server.port=8081
The following log shows, with the first error being 'UpnpListener encountered an error. Shutting down'.
The text was updated successfully, but these errors were encountered: