Serviio Console Remote - Connectivity is not established

Hello, i am a new member, and I barely using Serviio for 3 days and buy the pro.

But, when I want to actively the remote, show notification (CONNECTIVITY IS NOT ESTABLISHED)

Please, help me... Because of "remote" I buy this Serviio

What should I do???

Thank you in advance

P.s : My file is in my laptop. And I want to access my file from my smartphone (android) even my laptop is shutdown/off.
P.s.s: sorry about my engslish..

[atc98092]

If the laptop is shut off, there's no way to access the files on it from your smartphone or any other device. It has to be on and connected to your network.

No apologies necessary for your English, but I will need to ask some clarifying questions. Are you attempting to reach the MediaBrowser from outside your network? If so, that requires opening a port in your Internet router and forwarding that port to your laptop. This means your laptop needs to always have the same IP address on your network. While Serviio has the ability to configure your router automatically, it doesn't work with all routers, so you would have to do it manually.

If the laptop is shut off, there's no way to access the files on it from your smartphone or any other device. It has to be on and connected to your network.

No apologies necessary for your English, but I will need to ask some clarifying questions. Are you attempting to reach the MediaBrowser from outside your network? If so, that requires opening a port in your Internet router and forwarding that port to your laptop. This means your laptop needs to always have the same IP address on your network. While Serviio has the ability to configure your router automatically, it doesn't work with all routers, so you would have to do it manually.

Yes, I want to access my data from MediaBrowser.
Correct me if iam wrong, to connect to mediabrowser we need to set "remote," am I right? And i have been tried it, and Serviio said, "The network is not established"
and, what should I do know?

[atc98092]

Yes, to use MediaBrowser you must set the access password on the remote page. As to the error you're seeing, I assume it appears when you click the save button. I'll have to let Zip address that, but you might enable detailed logging and then upload the log here. I'm not sure if that action makes a log entry, but couldn't hurt.

2016-06-22 18:45:36,262 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18656) and extractor EMBEDDED
2016-06-22 18:45:36,262 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18656) and extractor COVER_IMAGE_IN_FOLDER
2016-06-22 18:45:36,262 DEBUG [MediaItemDAOImpl] Getting file of media item 18659
2016-06-22 18:45:36,262 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18659) and extractor EMBEDDED
2016-06-22 18:45:36,262 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18659) and extractor COVER_IMAGE_IN_FOLDER
2016-06-22 18:45:36,262 DEBUG [MediaItemDAOImpl] Getting file of media item 18660
2016-06-22 18:45:36,262 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18660) and extractor EMBEDDED
2016-06-22 18:45:36,262 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18660) and extractor COVER_IMAGE_IN_FOLDER
2016-06-22 18:45:36,262 DEBUG [MediaItemDAOImpl] Getting file of media item 18661
2016-06-22 18:45:36,262 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18661) and extractor EMBEDDED
2016-06-22 18:45:36,262 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18661) and extractor COVER_IMAGE_IN_FOLDER
2016-06-22 18:45:36,262 DEBUG [MediaItemDAOImpl] Getting file of media item 18662
2016-06-22 18:45:36,262 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18662) and extractor EMBEDDED
2016-06-22 18:45:36,262 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18662) and extractor COVER_IMAGE_IN_FOLDER
2016-06-22 18:45:36,262 DEBUG [MediaItemDAOImpl] Getting file of media item 18663
2016-06-22 18:45:36,262 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18663) and extractor EMBEDDED
2016-06-22 18:45:36,262 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18663) and extractor COVER_IMAGE_IN_FOLDER
2016-06-22 18:45:36,262 DEBUG [MediaItemDAOImpl] Getting file of media item 18664
2016-06-22 18:45:36,278 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18664) and extractor EMBEDDED
2016-06-22 18:45:36,278 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18664) and extractor COVER_IMAGE_IN_FOLDER
2016-06-22 18:45:36,278 DEBUG [MediaItemDAOImpl] Getting file of media item 18665
2016-06-22 18:45:36,278 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18665) and extractor EMBEDDED
2016-06-22 18:45:36,278 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18665) and extractor COVER_IMAGE_IN_FOLDER
2016-06-22 18:45:36,278 DEBUG [MediaItemDAOImpl] Getting file of media item 18666
2016-06-22 18:45:36,278 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18666) and extractor EMBEDDED
2016-06-22 18:45:36,278 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18666) and extractor COVER_IMAGE_IN_FOLDER
2016-06-22 18:45:36,278 DEBUG [MediaItemDAOImpl] Getting file of media item 18667
2016-06-22 18:45:36,278 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18667) and extractor EMBEDDED
2016-06-22 18:45:36,278 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18667) and extractor COVER_IMAGE_IN_FOLDER
2016-06-22 18:45:36,278 DEBUG [MediaItemDAOImpl] Getting file of media item 18668
2016-06-22 18:45:36,278 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18668) and extractor EMBEDDED
2016-06-22 18:45:36,278 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18668) and extractor COVER_IMAGE_IN_FOLDER
2016-06-22 18:45:36,278 DEBUG [MediaItemDAOImpl] Getting file of media item 18669
2016-06-22 18:45:36,278 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18669) and extractor EMBEDDED
2016-06-22 18:45:36,278 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18669) and extractor COVER_IMAGE_IN_FOLDER
2016-06-22 18:45:36,278 DEBUG [MediaItemDAOImpl] Getting file of media item 18670
2016-06-22 18:45:36,278 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18670) and extractor EMBEDDED
2016-06-22 18:45:36,278 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18670) and extractor COVER_IMAGE_IN_FOLDER
2016-06-22 18:45:36,278 DEBUG [MediaItemDAOImpl] Getting file of media item 18671
2016-06-22 18:45:36,278 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18671) and extractor EMBEDDED
2016-06-22 18:45:36,278 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18671) and extractor COVER_IMAGE_IN_FOLDER
2016-06-22 18:45:36,278 DEBUG [MediaItemDAOImpl] Getting file of media item 18684
2016-06-22 18:45:36,278 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18684) and extractor EMBEDDED
2016-06-22 18:45:36,278 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 18684) and extractor COVER_IMAGE_IN_FOLDER
2016-06-22 18:45:36,278 DEBUG [MediaItemDAOImpl] Reading dirty MediaItems for Repository (id = 106)
2016-06-22 18:45:36,294 DEBUG [RepositoryDAOImpl] Marking Repository 106 as scanned with current timestamp
2016-06-22 18:45:36,294 DEBUG [LibraryOneTimeScanner] Finished the scan of the library
2016-06-22 18:45:36,294 DEBUG [PipeManager] Enabling processing Delta scan queue
2016-06-22 18:45:39,188 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2016-06-22 18:45:39,860 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:53427s
2016-06-22 18:45:40,172 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:53427s
2016-06-22 18:45:40,485 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:53427s
2016-06-22 18:45:44,193 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2016-06-22 18:45:49,200 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2016-06-22 18:45:49,899 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:47164s
2016-06-22 18:45:50,211 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:47164s
2016-06-22 18:45:50,508 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:47164s
2016-06-22 18:45:54,205 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2016-06-22 18:45:59,206 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2016-06-22 18:45:59,940 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:47686s
2016-06-22 18:46:00,237 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:47686s
2016-06-22 18:46:00,550 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:47686s
2016-06-22 18:46:04,204 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2016-06-22 18:46:09,218 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2016-06-22 18:46:14,229 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2016-06-22 18:46:19,241 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2016-06-22 18:46:24,246 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2016-06-22 18:46:29,256 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2016-06-22 18:46:34,256 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2016-06-22 18:46:35,959 DEBUG [FeedUpdaterWorker] Checking for new and expired online resources
2016-06-22 18:46:35,959 DEBUG [OnlineRepositoryDAOImpl] Reading all OnlineRepositories
2016-06-22 18:46:36,705 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:49993s
2016-06-22 18:46:37,011 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:49993s
2016-06-22 18:46:37,317 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:49993s
2016-06-22 18:46:39,254 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2016-06-22 18:46:44,260 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2016-06-22 18:46:46,736 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:42094s
2016-06-22 18:46:47,046 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:42094s
2016-06-22 18:46:47,354 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:42094s
2016-06-22 18:46:49,270 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2016-06-22 18:46:54,281 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2016-06-22 18:46:56,774 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:51462s
2016-06-22 18:46:56,979 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:51462s
2016-06-22 18:46:57,278 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:51462s
2016-06-22 18:46:59,283 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2016-06-22 18:47:04,296 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2016-06-22 18:47:06,704 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:39329s
2016-06-22 18:47:07,001 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:39329s
2016-06-22 18:47:07,314 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:39329s
2016-06-22 18:47:09,311 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2016-06-22 18:47:14,318 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2016-06-22 18:47:16,741 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:33816s
2016-06-22 18:47:17,038 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:33816s
2016-06-22 18:47:17,350 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:33816s
2016-06-22 18:47:19,330 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2016-06-22 18:47:24,338 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2016-06-22 18:47:26,774 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:48868s
2016-06-22 18:47:27,083 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:48868s
2016-06-22 18:47:27,404 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:48868s
2016-06-22 18:47:29,344 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2016-06-22 18:47:29,603 DEBUG [ActionsServerResource] Action with name 'checkPortMapping' was requested
2016-06-22 18:47:29,604 DEBUG [ExternalIPRetriever] Retrieving external IP address
2016-06-22 18:47:30,060 DEBUG [ExternalIPRetriever] Found external IP address: 139.194.192.26
2016-06-22 18:47:30,060 INFO [PortMappingChecker] Running a check for external mapping of port 23424 on '139.194.192.26'
2016-06-22 18:47:33,508 INFO [YouGetSignalPortCheckerProvider] Port 23424 is closed
2016-06-22 18:47:34,347 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2016-06-22 18:47:35,969 DEBUG [FeedUpdaterWorker] Checking for new and expired online resources
2016-06-22 18:47:35,969 DEBUG [OnlineRepositoryDAOImpl] Reading all OnlineRepositories
2016-06-22 18:47:36,809 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:51857s
2016-06-22 18:47:37,106 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:51857s
2016-06-22 18:47:37,418 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.0.14:51857s

Thats my log file, anyway, thank you for your help

[atc98092]

I do see in the log that your router does not have port 23424 opened, so perhaps that is the issue. As I said, the auto-configure doesn't always work, so you would have to open it manually. I can't help you with doing that, because every router does it differently. I'd have to know the make and model of your router, and try to find a manual online.

Remember also, if you want this ability, your Serviio computer needs to always have the same IP address when on your home network. This can be done in two ways: assign a static IP address, or make an address reservation in your router (which is likely the device on your network that assigns IP addresses). Don't forget that the Serviio computer must always be turned on and connected to your home network to access your media.

Oke, i see.

Honestly, I have been tried this solution http://www.serviio.org/component/conten ... ote_access
but when I registered to portforward.com for forward my port, I do not accept email feedback for register.
I also tried to to make my IP static with dnsdynamic.org, but nothing changes.

One last thing, when I shared my folder song, all songs in some album not worked correctly. I streaming from android, and format song is FLAC.



what should I do?

[atc98092]

dnsdynamic.org does not give you a static IP, it simply registers your current public IP address with the root DNS servers on the Internet. You have to run the client on a computer on your network so it can detect a change to your public IP address and update the servers. I was referring to the private IP address assigned to your laptop within your network. When you set up port forwarding in your router, it needs to point to the correct internal IP address.

I didn't look closely at portforward.com. Not sure why a registration is necessary with them. For using a dynamic public IP address, I use DNSExit.com. dnsdynamic.org discontinued their free DDNS service, and DNSExit has been rock solid for me.

As to why you are having problems with your Android device, I can't help. I have no knowledge about Android.

dnsdynamic.org does not give you a static IP, it simply registers your current public IP address with the root DNS servers on the Internet. You have to run the client on a computer on your network so it can detect a change to your public IP address and update the servers. I was referring to the private IP address assigned to your laptop within your network. When you set up port forwarding in your router, it needs to point to the correct internal IP address.

I didn't look closely at portforward.com. Not sure why a registration is necessary with them. For using a dynamic public IP address, I use DNSExit.com. dnsdynamic.org discontinued their free DDNS service, and DNSExit has been rock solid for me.

As to why you are having problems with your Android device, I can't help. I have no knowledge about Android.

Oke, i will try DNSExit

Thank you for your help