Jump to content

Problem send message


yow888
 Share

Recommended Posts

yow888

Hello, I am using emby server on a synology NAS.

Remote access works fine, but sending a message from an external connection does not work.
I have the icon that appears but when I send the message nothing happens.

My network settings are as follows:

Public http port number: 80
Public https port number: 443

External domain: emby.my-domain.com

Secure connection mode:
Managed by a reverse proxy

On the nas the reverse proxy is configured like this:

Souce
Protocol: HTTPS
Host name: emby.my-domain.com
Port : 443

Destination
Protocol: HTTP
Hostname: HTTP
Port: 8096

Of course, my port 443 is open on the firewall and on the box

Thank you for your help

Emby version 4.6.4.0 - DSM 7.0-41890

Link to comment
Share on other sites

Hi there, can we please look at an example?

Thanks !

Link to comment
Share on other sites

Happy2Play

@Lukeisn't Send message limited to in network devices?  Or is that just specific devices?

Link to comment
Share on other sites

yow888

Hello, thank you for your quick response. Here are the pictures of my setup.

Messages work well remotely if the connection is not secure. But as soon as the URL is https they no longer work

Dsm config.png

Emby config.png

Link to comment
Share on other sites

21 hours ago, Happy2Play said:

@Lukeisn't Send message limited to in network devices?  Or is that just specific devices?

No as mess with my son and daughter using that at times and they both live in different locations and states. :)

Link to comment
Share on other sites

OK please attach the emby server log from when you tried to send the message. Thanks.

Link to comment
Share on other sites

On 10/12/2021 at 7:06 PM, Happy2Play said:

@Lukeisn't Send message limited to in network devices?  Or is that just specific devices?

Depends on the device.  It won't work with a Roku, for instance.

Link to comment
Share on other sites

yow888
25 minutes ago, Luke said:

OK please attach the emby server log from when you tried to send the message. Thanks.

2021-10-14 17:46:36.523 Info Server: http/1.1 Response 200 to 92.184.106.231. Time: 0ms. http://emby.yow.ovh/emby/Sessions/ede74217d14dd8d989d10ed5e89d7477/Message?X-Emby-Client=Emby for iOS&X-Emby-Device-Name=iPhone de Yohann Yo&X-Emby-Device-Id=9198F63E-71BC-499A-94A9-0D8E70EDF0F3&X-Emby-Client-Version=2.0.10
2021-10-14 17:46:36.579 Info Server: http/1.1 POST http://emby.yow.ovh/emby/Sessions/ede74217d14dd8d989d10ed5e89d7477/Message?X-Emby-Client=Emby for iOS&X-Emby-Device-Name=iPhone de Yohann Yo&X-Emby-Device-Id=9198F63E-71BC-499A-94A9-0D8E70EDF0F3&X-Emby-Client-Version=2.0.10. UserAgent: Mozilla/5.0 (iPhone; CPU iPhone OS 15_0_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148
2021-10-14 17:46:36.582 Info Server: http/1.1 Response 204 to 92.184.106.231. Time: 3ms. http://emby.yow.ovh/emby/Sessions/ede74217d14dd8d989d10ed5e89d7477/Message?X-Emby-Client=Emby for iOS&X-Emby-Device-Name=iPhone de Yohann Yo&X-Emby-Device-Id=9198F63E-71BC-499A-94A9-0D8E70EDF0F3&X-Emby-Client-Version=2.0.10
2021-10-14 17:46:42.898 Info Server: http/1.1 POST http://emby.yow.ovh/Sessions/ff27bc83d850b2c055f612603ad0738f/Message?X-Emby-Client=Emby Web&X-Emby-Device-Name=Safari&X-Emby-Device-Id=9a127b72-abd2-44b9-a1e5-e820857973c3&X-Emby-Client-Version=4.6.4.0. UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.0 Safari/605.1.15

Hello, here are the logs when sending a message.

1 device on the same network as the Emby server and the second external.
Messages sent from the computer on the same network as Emby arrive, however those sent from outside do not arrive.

embyserver.txt

Link to comment
Share on other sites

yow888
Il y a 1 minute, Luke a dit :

À quel appareil essayez-vous d'envoyer ?

Sending from a mac (Safari) to Iphone ok

Sending from iphone to mac does not work

Link to comment
Share on other sites

What do you mean to mac? Is that with the web app on the mac, or our MacOS app?

Link to comment
Share on other sites

  • 2 weeks later...

@yow888 was the web browser receiving the command in the foreground of the desktop? Had it been idle for a long period of time?

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...