Jump to content

Error connecting to the remote Media Browser repository


Snowfalcon

Recommended Posts

Snowfalcon

Using server version 3.0.5233.40306. This happened after restarting the server.  Attached is a log file.

 

 

Edited by Snowfalcon
Link to comment
Share on other sites

No big deal.  Its the weekend and we've just put out a new release.  Our servers are overloaded.

 

We're working on upgrading our infrastructure so hopefully we can handle this better.

Link to comment
Share on other sites

Snowfalcon

It has been almost a week now and still get the same error message.  Do you need a new log file.  Thanks in advance for your help

Link to comment
Share on other sites

It has been almost a week now and still get the same error message.  Do you need a new log file.  Thanks in advance for your help

 

Is everything still functioning properly?  It would be possible to have this occur once or twice but then not fail and we'd go on about our business.

Link to comment
Share on other sites

Snowfalcon

Here is a extract from the log.  It will not connect to the server

2014-05-12 19:21:05.6623 Error - App: Error getting response from http://mediabrowser3.com/community/index.php?/blog/rss/1-media-browser-developers-blog
2014-05-12 19:21:05.6648 Error - App: Error downloading news
2014-05-12 19:21:05.6973 Error - App: Error getting response from http://www.mb3admin.com/admin/service/MB3ServerNotifications.json
2014-05-12 19:21:05.6973 Error - App: Error downloading remote notifications

Everything seems to be functioning just can't update anything
 

Link to comment
Share on other sites

That is very disappointing.  Are you sure it is only us and not a more broad issue with your internet connection?

Link to comment
Share on other sites

Snowfalcon

You were correct come to find out my firewall was blocking the connection. Everything is good now. Thanks for the help :D

Link to comment
Share on other sites

Whew!  We just executed a move to a brand new environment and performance and availability have been much improved so far so it would have been surprising for this to be an issue on our end.  Glad you got it figured out.

  • Like 1
Link to comment
Share on other sites

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...