Can't Access Serviio Remotely

Hello,

I have opened up the specified port 23424 and I can't remotely access my Serviio.

I have entered the ip address and the :23424 and /mediabrowser after it, and it just says error site can't be reached.

This worked before I moved. I got new internet after I moved and now it won't work.

macOS HIgh Sierra 10.13.6
3.6 ghz Intel Core i5
16 GB Memory 1333 MhZ DDR3
2 TB HD
ATI Radeon 5750 1024 MB
12 MB/s Internet Connection

[zip]

Do you get a green tick when you check connectivity on the Remote tab in the console?

If not, double check the router that 23423 is indeed open and forwards to your Mac/s IP ddress

Do you get a green tick when you check connectivity on the Remote tab in the console?

If not, double check the router that 23423 is indeed open and forwards to your Mac/s IP ddress

It is showing the green check mark by "insecure connectivity" and a red x by "Secure Connectivity".

I am able to finally access it from an external internet connection. Checked the router and port is open now.

How do I get it enable secure connectivity?

[atc98092]

Do you get a green tick when you check connectivity on the Remote tab in the console?

If not, double check the router that 23423 is indeed open and forwards to your Mac/s IP ddress

It is showing the green check mark by "insecure connectivity" and a red x by "Secure Connectivity".

I am able to finally access it from an external internet connection. Checked the router and port is open now.

How do I get it enable secure connectivity?

Secure requires opening port 23523, and using that port number in the URL that you use to connect to MediaBrowser.

Do you get a green tick when you check connectivity on the Remote tab in the console?

If not, double check the router that 23423 is indeed open and forwards to your Mac/s IP ddress

It is showing the green check mark by "insecure connectivity" and a red x by "Secure Connectivity".

I am able to finally access it from an external internet connection. Checked the router and port is open now.

How do I get it enable secure connectivity?

Secure requires opening port 23523, and using that port number in the URL that you use to connect to MediaBrowser.

Screen Shot 2019-04-28 at 16.26.43.png (50.99 KiB) Viewed 19007 times

The port appears to be opened in the router configuration.

[atc98092]

You've opened every port between 23424 and 23524. I suggest changing it back to a single port and add a second forwarding rule. You're really opened your router up this way. If I recognize it correctly, that's a Netgear router. It's possible that entering a port range doesn't work on them, so even with both numbers it might still only be forwarding the first port.

Also, when you are attempting to use the secure port, remember the URL has to start with HTTPS, not HTTP.

You've opened every port between 23424 and 23524. I suggest changing it back to a single port and add a second forwarding rule. You're really opened your router up this way. If I recognize it correctly, that's a Netgear router. It's possible that entering a port range doesn't work on them, so even with both numbers it might still only be forwarding the first port.

Also, when you are attempting to use the secure port, remember the URL has to start with HTTPS, not HTTP.

Alright, I will try that. Thank you.

Not trying to hijack this conversation but I'm having a similar situation. I have tried the "auto configure" and manually configuring too but I always get a green check for Insecure connectivity and a red X for Secure connectivity. I have tried setting the router's protocol for the port to "both" and "tcp" and get the same results. Consequently, the Alexa skill cannot connect properly.

Ideas?

Thank you!

Marc

[atc98092]

Not trying to hijack this conversation but I'm having a similar situation. I have tried the "auto configure" and manually configuring too but I always get a green check for Insecure connectivity and a red X for Secure connectivity. I have tried setting the router's protocol for the port to "both" and "tcp" and get the same results. Consequently, the Alexa skill cannot connect properly.

Ideas?

Thank you!

Marc

When you manually configured your router, confirm that you forwarded ports 23424 and 23524 to your Serviio computer? You have to do both ports, one for HTTP and one for HTTPS.

Yes...I have forwarded both ports as TCP (I did try both) to my server;

Annotation 2019-05-13 071125.png (11.11 KiB) Viewed 18908 times

One more piece of info: if I try to connect locally (https://192.168.1.51:23524) I get a message in the browser that says "Not Found".

Is this expected behavior?

[atc98092]

One more piece of info: if I try to connect locally (https://192.168.1.51:23524) I get a message in the browser that says "Not Found".

Is this expected behavior?

You have to include /mediabrowser after the port (https://192.168.1.51:23524/mediabrowser). I tried it on mine and it worked after I added that. I've never attempted external secure access, so can't say if mine would work that way as well.

I found this in the DEBUG log;

2019-05-13 08:43:26,983 DEBUG [ActionsServerResource] Action with name 'checkSSLPortMapping' was requested
2019-05-13 08:43:26,983 DEBUG [ActionsServerResource] Action with name 'checkPortMapping' was requested
2019-05-13 08:43:26,988 DEBUG [PortMappingChecker] Running a check for external mapping of port 23524 on '73.239.202.226'
2019-05-13 08:43:27,552 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2019-05-13 08:43:28,343 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2019-05-13 08:43:28,385 DEBUG [YouGetSignalPortCheckerProvider] Cannot work out whether port 23524 is open or closed
2019-05-13 08:43:28,386 DEBUG [PortMappingChecker] Running a check for external mapping of port 23424 on '73.239.202.226'
2019-05-13 08:43:28,612 DEBUG [PortMappingChecker] Failed to retrieve open port information
java.io.IOException: java.io.IOException: Received status 302
at org.serviio.upnp.service.contentdirectory.rest.access.CanYouSeeMePortCheckerProvider.isPortOpen(CanYouSeeMePortCheckerProvider.java:71)
at org.serviio.upnp.service.contentdirectory.rest.access.PortMappingChecker.isPortOpen(PortMappingChecker.java:45)
at org.serviio.ui.resources.server.ActionsServerResource.checkPortMapping(ActionsServerResource.java:176)
at org.serviio.ui.resources.server.ActionsServerResource.execute(ActionsServerResource.java:75)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.restlet.resource.ServerResource.doHandle(ServerResource.java:521)
at org.restlet.resource.ServerResource.post(ServerResource.java:1346)
at org.restlet.resource.ServerResource.doHandle(ServerResource.java:621)
at org.restlet.resource.ServerResource.doNegotiatedHandle(ServerResource.java:679)
at org.restlet.resource.ServerResource.doConditionalHandle(ServerResource.java:357)
at org.serviio.restlet.AbstractServerResource.doConditionalHandle(AbstractServerResource.java:49)
at org.restlet.resource.ServerResource.handle(ServerResource.java:1014)
at org.restlet.resource.Finder.handle(Finder.java:246)
at org.restlet.routing.Filter.doHandle(Filter.java:159)
at org.restlet.routing.Filter.handle(Filter.java:206)
at org.restlet.routing.Router.doHandle(Router.java:431)
at org.restlet.routing.Router.handle(Router.java:648)
at org.restlet.routing.Filter.doHandle(Filter.java:159)
at org.restlet.routing.Filter.handle(Filter.java:206)
at org.restlet.routing.Filter.doHandle(Filter.java:159)
at org.restlet.engine.application.StatusFilter.doHandle(StatusFilter.java:155)
at org.restlet.routing.Filter.handle(Filter.java:206)
at org.restlet.routing.Filter.doHandle(Filter.java:159)
at org.restlet.routing.Filter.handle(Filter.java:206)
at org.restlet.engine.CompositeHelper.handle(CompositeHelper.java:211)
at org.restlet.engine.application.ApplicationHelper.handle(ApplicationHelper.java:84)
at org.restlet.Application.handle(Application.java:384)
at org.restlet.routing.Filter.doHandle(Filter.java:159)
at org.restlet.routing.Filter.handle(Filter.java:206)
at org.restlet.routing.Router.doHandle(Router.java:431)
at org.restlet.routing.Router.handle(Router.java:648)
at org.restlet.routing.Filter.doHandle(Filter.java:159)
at org.restlet.routing.Filter.handle(Filter.java:206)
at org.restlet.routing.Router.doHandle(Router.java:431)
at org.restlet.routing.Router.handle(Router.java:648)
at org.restlet.routing.Filter.doHandle(Filter.java:159)
at org.restlet.engine.application.StatusFilter.doHandle(StatusFilter.java:155)
at org.restlet.routing.Filter.handle(Filter.java:206)
at org.restlet.routing.Filter.doHandle(Filter.java:159)
at org.restlet.routing.Filter.handle(Filter.java:206)
at org.restlet.engine.CompositeHelper.handle(CompositeHelper.java:211)
at org.restlet.Component.handle(Component.java:406)
at org.restlet.Server.handle(Server.java:516)
at org.restlet.engine.connector.ServerHelper.handle(ServerHelper.java:72)
at org.restlet.engine.adapter.HttpServerHelper.handle(HttpServerHelper.java:152)
at org.restlet.ext.simple.internal.SimpleContainer.handle(SimpleContainer.java:80)
at org.simpleframework.http.core.Dispatcher.dispatch(Dispatcher.java:121)
at org.simpleframework.http.core.Dispatcher.run(Dispatcher.java:103)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: Received status 302
at org.serviio.upnp.service.contentdirectory.rest.access.CanYouSeeMePortCheckerProvider.isPortOpen(CanYouSeeMePortCheckerProvider.java:68)
... 53 more

Including "mediabrowser" did work! Ok...so how come when I click "Check connectivity status" on the remote page the secure check always fails?

And for the record I assume I need the secure connection for the Alexa skill - yes?

I tested the port forwarding with "https://www.yougetsignal.com/tools/open-ports/" and it reports 23424 as valid and 23524 as invalid!

Any ideas why this port is invalid? Also, I created a 2nd entry in the port forwarding table for 23524 so the two ports each have their own entry...and no difference...it's still invalid.

I have to believe its a setting in serviio or the OS but have no idea where to look.

[Meelis]

I tested the port forwarding with "https://www.yougetsignal.com/tools/open-ports/" and it reports 23424 as valid and 23524 as invalid!

Any ideas why this port is invalid? Also, I created a 2nd entry in the port forwarding table for 23524 so the two ports each have their own entry...and no difference...it's still invalid.

I have to believe its a setting in serviio or the OS but have no idea where to look.

Disable your firewall and antivirus and see what happent's then.

[atc98092]

I tested the port forwarding with "https://www.yougetsignal.com/tools/open-ports/" and it reports 23424 as valid and 23524 as invalid!

Any ideas why this port is invalid? Also, I created a 2nd entry in the port forwarding table for 23524 so the two ports each have their own entry...and no difference...it's still invalid.

I have to believe its a setting in serviio or the OS but have no idea where to look.

No setting in Serviio. Those ports are hard baked into its configuration. They can be changed, but not easily. But it does sound like something in the OS or security software is blocking it.

Meelis - Disable your firewall and antivirus and see what happent's then.

I'm running Serviio on a Raspberry Pi...no firewall or antivirus on the Pi.

Also, I followed the instruction here on the board to set up Apache2 and a certificate...still no love...still get a red X for secure connection

For the record I followed the instructions in the post: viewtopic.php?f=5&t=24520&hilit=certbot

And this still did not enable the secure connection

Ideas?