Jump to content

Recommended Posts

Posted

Hi,

 

I'd like to opt-out for registering my server with Emby Connect. Currently I don't see any options to do this, could you implement one?

 

Thanks

bluemonkey07
Posted

There is no need just don't use it and sign in manually.if you already are using it just log out and then again just select the manual sign in option

Posted

You can sign in using the "Emby Connect" link up at the top of this page. Sign in. On the server select screen hit the 3 dots and delete the server.

Posted (edited)

There is no need just don't use it and sign in manually.if you already are using it just log out and then again just select the manual sign in option

I have never signed up for it and yet Emby phones home. That's exactly what I want to disable.

 

You can sign in using the "Emby Connect" link up at the top of this page. Sign in. On the server select screen hit the 3 dots and delete the server.

I doubt this will remove the server registration either, it just removes the association to your account.

 

Thanks for suggestions though.

Edited by jani
bluemonkey07
Posted (edited)

What exactly is your issue and what are you trying to achieve then? Emby server phones home occasionally to check premiere status and anonymous usage data (which you can opt out of) I believe

Edited by Vidman
Happy2Play
Posted

Anonymous usage reporting is on Dashboard-Settings.

Posted

What exactly is your issue and what are you trying to achieve then? Emby server phones home occasionally to check premiere status and anonymous usage data (which you can opt out of) I believe

I do not want my server registered in an arbitrary registry.

Happy2Play
Posted (edited)

It's not the only way it gets linked is if you add your Connect/Forum account name in Users-User-Profile.  So if you attempt to login with connect and you don't have a linked user you will get nothing.

 

578c887f9b2aa_connect.jpg

 

578c8a1e70be2_conn.jpg

Edited by Happy2Play
bluemonkey07
Posted (edited)

It's not. The only way it gets linked is if you add your Connect/Forum account name in Users-User-Profile. So if you attempt to login with connect and you don't have a linked user you will get nothing.

 

578c887f9b2aa_connect.jpg

 

578c8a1e70be2_conn.jpg

Added punctuation to make the meaning more clear ;) Edited by Vidman
Posted

I would think that a larger percent of us are only using EMBY locally within our own home/network and have no need for EMBY Connect, so I think being able to disable it would be a smart feature.

 

In fact I would suggest that it be disabled by default and only if you want to enable remote access to your Emby Server would you have a need to enable it.

bluemonkey07
Posted

It is"disabled" by default.... It's an opt in feature

  • Like 2
pir8radio
Posted (edited)

Windows 7?   Can't you just go into C:\windows\system32\drivers\hosts    edit with notepad, and add lines like this, or whatever other domain names you want to keep that machine from reaching?   

Windows 10 hosts file is here: C:\windows\system32\drivers\etc\hosts

 

Find out what emby domain names you want to block and add them 

to the below list in hosts file.

--- Add the below lines to bottom of the file ---

 

0.0.0.0       connect.emby.media
0.0.0.0       bot.whatismyipaddress.com
 
 
Again, just my opinion, but emby is made to be easy to setup and run, for the vast majority of users...  We can't expect them to add 500 options to cover all of the goofy things each of us are doing, in the process, making it difficult for the masses... For power users, we are all smart, we just need to find a solution on our own..  It's often as easy as a few lines in a text file.....   ;)
Edited by pir8radio
  • Like 1
  • 5 months later...
Posted

I too would like to see this a a feature (checkbox) right next to the existing "Enable anonymous usage reporting" I don't have an issue with it being on by default, as long as I can turn it off.  Using host files or firewalls to block the URL will only generate errors in the logs, and who knows if it breaks any internal checks if it's not able to register itself (even though you're not using it for remote access).

Happy2Play
Posted

If you never enter your username/email address under users then connect will never work unless you manually enter all the information.  So you the user have to opt in and enter all the information for this feature to work.

pir8radio
Posted (edited)

I too would like to see this a a feature (checkbox) right next to the existing "Enable anonymous usage reporting" I don't have an issue with it being on by default, as long as I can turn it off.  Using host files or firewalls to block the URL will only generate errors in the logs, and who knows if it breaks any internal checks if it's not able to register itself (even though you're not using it for remote access).

 

It works fine on my setup. I am a lifetimer

Edited by pir8radio
Posted

If you never enter your username/email address under users then connect will never work unless you manually enter all the information.  So you the user have to opt in and enter all the information for this feature to work.

 

I don't enter email address for my users, but I do block the connect URL in my firewall and I can see errors because of it.

2016-12-23 21:16:04.0431 Error ConnectManager: Error registering with Connect	*** Error Report ***	Version: 3.1.1.0	Command line: C:\Users\<userID>\AppData\Roaming\MediaBrowser-Server\System\MediaBrowser.ServerApplication.exe	Operating system: Microsoft Windows NT 6.2.9200.0	64-Bit OS: True	64-Bit Process: True	Processor count: 4	Program data path: C:\Users\<userID>\AppData\Roaming\MediaBrowser-Server	Application directory: C:\Users\<UserID>\AppData\Roaming\MediaBrowser-Server\System	System.Net.WebException: The server committed a protocol violation. Section=ResponseStatusLine	   at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context)	   at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult)	   at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)	--- End of stack trace from previous location where exception was thrown ---	   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)	   at Emby.Common.Implementations.HttpClientManager.HttpClientManager.<SendAsyncInternal>d__20.MoveNext()	--- End of stack trace from previous location where exception was thrown ---	   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)	   at Emby.Common.Implementations.HttpClientManager.HttpClientManager.<SendAsync>d__17.MoveNext()	--- End of stack trace from previous location where exception was thrown ---	   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)	   at Emby.Server.Implementations.Connect.ConnectManager.<UpdateServerRegistration>d__37.MoveNext()	--- End of stack trace from previous location where exception was thrown ---	   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)	   at Emby.Server.Implementations.Connect.ConnectManager.<UpdateConnectInfoInternal>d__31.MoveNext()	System.Net.WebException	   at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context)	   at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult)	   at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)	--- End of stack trace from previous location where exception was thrown ---	   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)	   at Emby.Common.Implementations.HttpClientManager.HttpClientManager.<SendAsyncInternal>d__20.MoveNext()	--- End of stack trace from previous location where exception was thrown ---	   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)	   at Emby.Common.Implementations.HttpClientManager.HttpClientManager.<SendAsync>d__17.MoveNext()	--- End of stack trace from previous location where exception was thrown ---	   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)	   at Emby.Server.Implementations.Connect.ConnectManager.<UpdateServerRegistration>d__37.MoveNext()	--- End of stack trace from previous location where exception was thrown ---	   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)	   at Emby.Server.Implementations.Connect.ConnectManager.<UpdateConnectInfoInternal>d__31.MoveNext()

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
×
×
  • Create New...