kira yamato 21 Posted February 17, 2025 Author Posted February 17, 2025 1 hour ago, Luke said: Hi, did you see this? My remote connect is working for now, but I’m confused about CORS Origin. It’s too technical for me to understand. Can you explain it in a simpler way so I can fix it? 1
Luke 42077 Posted March 9, 2025 Posted March 9, 2025 On 2/17/2025 at 12:25 AM, kira yamato said: My remote connect is working for now, but I’m confused about CORS Origin. It’s too technical for me to understand. Can you explain it in a simpler way so I can fix it? Hi, were you able to figure it out?
kira yamato 21 Posted April 18, 2025 Author Posted April 18, 2025 On 3/9/2025 at 3:08 PM, Luke said: Hi, were you able to figure it out? No, the same problem has returned. Could you please assist me in changing the CORS Origin setting to the default to *
Thidsa 44 Posted April 27, 2025 Posted April 27, 2025 In my case it was my reverse proxy that needed the setting "CORS Origin set to *". Dont know if @kira yamatois using one. Dont remember if IOS devices could connect at the time if i had opened a port for emby, as all of my things just worked at the time through my reverse proxy except for IOS devices connecting to emby. Haven't had a port opened for emby for years, changed reverse proxy awhile ago and then 2.2.31 emby happened when it was released. Found the CORS setting at proxy developer site. Just tried to open port 8096 and connect with a ios device with emby 2.2.37 to http://myddns:8096 and it worked right away. So if it is just that he has problem with, im not so sure I know what it could be. 1
kira yamato 21 Posted May 6, 2025 Author Posted May 6, 2025 On 3/9/2025 at 3:08 PM, Luke said: Hi, were you able to figure it out? I realize that this issue occurs when the router reboots and the public IP address changes. Even though the new IP address is displayed in the Emby dashboard, the remote access is not working. I discovered that restarting the router again, while the computer is open and the Emby program is restarted, resolves the problem. Based on this information, do you know what causes this problem? and why it only affect iOS devices?
Luke 42077 Posted May 6, 2025 Posted May 6, 2025 16 hours ago, kira yamato said: I realize that this issue occurs when the router reboots and the public IP address changes. Even though the new IP address is displayed in the Emby dashboard, the remote access is not working. I discovered that restarting the router again, while the computer is open and the Emby program is restarted, resolves the problem. Based on this information, do you know what causes this problem? and why it only affect iOS devices? Are you signing in with Emby Connect, or by entering server information manually?
kira yamato 21 Posted May 7, 2025 Author Posted May 7, 2025 3 hours ago, Luke said: Are you signing in with Emby Connect, or by entering server information manually? Both Emby Connect and manually IP address are not working at all.
Luke 42077 Posted May 7, 2025 Posted May 7, 2025 15 hours ago, kira yamato said: Both Emby Connect and manually IP address are not working at all. Hi, maybe this is because you entered the old address after it had changed?
kira yamato 21 Posted May 7, 2025 Author Posted May 7, 2025 1 minute ago, Luke said: Hi, maybe this is because you entered the old address after it had changed? No, I double-checked that I had entered the new, correct IP address.i assume that the Emby app on iOS at first it still uses the LAN internal IP instead of the public IP. However, when the public IP changes again, it somehow works.
sa2000 674 Posted May 7, 2025 Posted May 7, 2025 After a router reboot you got a new public ip address - maybe you also got a new local ip address for the server and if so then the existing port forward would no longer go to the server is the local ip a dhcp reservation for the mac hardware address of the network card ? is the port forward done manually or automatically by emby server using upnp
kira yamato 21 Posted May 7, 2025 Author Posted May 7, 2025 1 minute ago, sa2000 said: After a router reboot you got a new public ip address - maybe you also got a new local ip address for the server and if so then the existing port forward would no longer go to the server is the local ip a dhcp reservation for the mac hardware address of the network card ? is the port forward done manually or automatically by emby server using upnp I configured this PC to use a fixed internal IP address and manually forward ports using that fixed IP address.
sa2000 674 Posted May 7, 2025 Posted May 7, 2025 And is the ip address within the dhcp range on the router ? If it is and not specified as reserved then it may get assigned by the router to another device
sa2000 674 Posted May 7, 2025 Posted May 7, 2025 (edited) Static IP addresses need to be outside the dhcp range otherwise DHCP reservation must also be used Edited May 7, 2025 by sa2000
kira yamato 21 Posted May 7, 2025 Author Posted May 7, 2025 (edited) 10 minutes ago, sa2000 said: And is the ip address within the dhcp range on the router ? If it is and not specified as reserved then it may get assigned by the router to another device I set a fixed IP address with a higher number than all the devices in my house. This way, it will always reserve that specific IP address.I thought this wasn’t a network setting because Android TV can always connect remotely to this server, while iOS cannot. Edited May 7, 2025 by kira yamato
kira yamato 21 Posted May 17, 2025 Author Posted May 17, 2025 (edited) On 5/7/2025 at 11:06 PM, Luke said: Hi, maybe this is because you entered the old address after it had changed? Hey, I noticed something peculiar this time. Public IP addresses remain constant, but there’s a strange issue here. First, I couldn’t remotely connect to my server using my iPhone’s 5G connection. So, I shared my hotspot with my iPad, and surprisingly, it managed to connect to my server! (i can still using manually put public ip to connect when in not auto sign)As I always say, the problem should be within the Emby app on iOS, not on the network or server side.(when this happend it seem that device cannot use maually login also its keep show last login as internal ip not remoteip) it try restart iphone and reinstall app it still cannot connect. Edited May 17, 2025 by kira yamato
Luke 42077 Posted May 31, 2025 Posted May 31, 2025 On 5/16/2025 at 11:50 PM, kira yamato said: Hey, I noticed something peculiar this time. Public IP addresses remain constant, but there’s a strange issue here. First, I couldn’t remotely connect to my server using my iPhone’s 5G connection. So, I shared my hotspot with my iPad, and surprisingly, it managed to connect to my server! (i can still using manually put public ip to connect when in not auto sign)As I always say, the problem should be within the Emby app on iOS, not on the network or server side.(when this happend it seem that device cannot use maually login also its keep show last login as internal ip not remoteip) it try restart iphone and reinstall app it still cannot connect. @kira yamatowere you able to solve this?
kira yamato 21 Posted May 31, 2025 Author Posted May 31, 2025 18 minutes ago, Luke said: @kira yamatowere you able to solve this? It’s fine for now. I recently discovered that my IPS randomly sent me an ad for their promotion through a redirect network to their page. I kindly requested that they refrain from doing this again after informing them that the issue hasn’t occurred yet. 1
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now