altramarine 21 Posted October 8, 2014 Share Posted October 8, 2014 (edited) Hi guys, I am looking for some ideas with my Roku situation. Approximately a day ago, my Roku 3 lost the ability to connect to MB server and for the life of me, I cannot figure out why. My relevant setup/legend: Location A (my house): Asus N66U Router: acts as VPN(OpenVPN) server ComputerA1: MB server 3.0.5390.25829 ComputerA2: HTPC with MBC Location B (parents): Asus N66U Router: acts as VPN client Roku 3 (via ethernet) with MB v1.63 channel which is configured with the local IP address/port of the Computer1 from Location A. Note: Location A and B are connected to each other via VPN. Mysterious facts: as of approximately a day ago, Roku presents with "Unable to connect" message when I attempt to open MediaBrowser channel. sometimes after unsuccessful connection, I end up in MB Roku options, where i see version (1.63), user selection option, which gives me the same unsuccessful connection dialog if pressed, and general settings. I am not sure if that equates to anything. all other channels are workings fine - internet is present able to connect to the MB server (Location A) via any other computer (Location B) by using web client (http://ComputerA1_localip:port/mediabrowser) or iphone/ipad - VPN is working correctly. able to connect to the MB server from any computer, MBC, iphone from Location A also all other VPN related services operate correctly: able to browse remote shares or access either side's permitted services. This issue, whatever it is, appears to affect only Roku, only the MB channel. For the sake of completeness, I tried using the old 1.17.6 MB channel with identical result. I cannot find anything in the MB server, Asus router logs that is relevant which is frustrating. I've uninstalled MB channel several times and each time I installed it back, the settings were retained. Is there a way to clear these settings after an uninstall? Any other suggestions? Thanks so much! Edited October 8, 2014 by altramarine Link to comment Share on other sites More sharing options...
speechles 1917 Posted October 8, 2014 Share Posted October 8, 2014 (edited) Your roku might have a wacky registry. Normally if any application is uninstalled the devID for it is removed from the registry. It will not be if multiple applications use the same devID and one of them is still installed. To alleviate all this, factory restore your roku. After it completes, do a system update. It will download and update all your apps you previously had installed and initialize their states. Paid, free, and beta channels. You wont have to remember what the roku had on it. This is the easiest way to solve the issue if it is just occurring on roku. Sent from my Nexus 7 using Tapatalk Edited October 8, 2014 by speechles 1 Link to comment Share on other sites More sharing options...
altramarine 21 Posted October 8, 2014 Author Share Posted October 8, 2014 Thanks Speechles, Now I feel silly for not trying it out first! This whole issue made me look high and low and now I've become aware of the Roku 3 WiFi Direct (connection to remote) which interferes with my wireless, but that is another issue. Link to comment Share on other sites More sharing options...
altramarine 21 Posted October 9, 2014 Author Share Posted October 9, 2014 Had the Roku3 factory reset, no go unfortunately. I tried connecting via Ethernet and wireless with same result. For kicks I decided to plug my old Roku 2 XD and bam...that works fine. This is some sort of mockery! haha! Is there a way to check the Roku3 logs to see what it is doing when attempting to connect to MB server? Many thanks, Link to comment Share on other sites More sharing options...
speechles 1917 Posted October 9, 2014 Share Posted October 9, 2014 http://sdkdocs.roku.com/display/sdkdoc/Developer+Guide#DeveloperGuide-70LoadingandRunningyourApplicationWalkthrough You would need your roku in developer mode, upload the zip from media browser for roku off github (link below) to your roku, and telnet your roku. Follow the guide above. Its not hard. https://github.com/MediaBrowser/MediaBrowser.Roku/blob/master/MediaBrowser.Roku.zip?raw=true You can only get debug from applications you have personally uploaded to your roku. You won't see debug on other applications. This is why you have to complete these steps. Sent from my Nexus 7 using Tapatalk Link to comment Share on other sites More sharing options...
altramarine 21 Posted October 9, 2014 Author Share Posted October 9, 2014 (edited) Funny, I am already on that page. Enabled the debug mode, thanks for the zip link. Getting there:) Thanks a lot! Edited October 9, 2014 by altramarine Link to comment Share on other sites More sharing options...
altramarine 21 Posted October 9, 2014 Author Share Posted October 9, 2014 (edited) I managed to enable the tcpdump and am receiving logs. I tried to connect to the MB sever a few times (via ROKU)) for logs to fill with relevant information. Loaded Wireshark and attempted to read through the generated log. I cannot seem to locate the IP the MB is supposed to connect to. It is mostly filled with telnet machine IP to ROKU ip chatter. Am I doing it wrong? Sorry, I am a bit over my head here. Many thanks again! Edited October 9, 2014 by altramarine Link to comment Share on other sites More sharing options...
speechles 1917 Posted October 9, 2014 Share Posted October 9, 2014 (edited) You need to send the application over and it boots into the application, or pick the application you previously uploaded. telnet [roku ip here] 8085 For me its.. telnet 192.168.1.239 8085 You don't need tcpdump and wireshark. You can also, if you don't have telnet.. lazy man approach Http://[roku ip here]:8085 in a browser suffices... When using the application zip you have uploaded this will spew debug() statements. This is the part needed to see what the hold up is and possibly if the brightscript interpreter crashed, and went into debugger mode. Sent from my Nexus 7 using Tapatalk Edited October 9, 2014 by speechles Link to comment Share on other sites More sharing options...
altramarine 21 Posted October 10, 2014 Author Share Posted October 10, 2014 Yes, I went too far ... as far as tcpdump. I learnt something new in the process though:) Unfortunately, telnet did not reveal anything useful, expect for "Unable to connect" message when I attempted to connect the MB server. I will try it again today on the working Roku2 XD and see what the difference between Roku 3 might be. Thank you very much for your help thus far! Link to comment Share on other sites More sharing options...
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