Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    ProGet Connector Timeout

    Scheduled Pinned Locked Moved Support
    2 Posts 2 Posters 22 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S Offline
      scott.wright_8356
      last edited by

      Hi Everyone,

      We have an issue with our ProGet server running 24.0.6. We have added some new caching feeds and getting the following error in the logs consistently a few times a day.

      Level:Warning
      Category:Connector
      Message:Unable to fetch connector data; using cached copy.
      Details:System.Net.WebException: The operation has timed out.
      at System.Net.HttpWebRequest.EndGetResponse(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 ---
      at System.Net.WebRequest.GetResponseAsync()
      at Inedo.ProGet.Feeds.Connector.GetDirectResponseAsync(String url)
      at Inedo.ProGet.Feeds.Connector.GetCachedResponseAsync(String url)
      

      We are unable to tell from the logs which connector is timing out. We want to check the network and firewall and ensure no errors for the public URL. Is there a way to determine this?

      Regards Scott

      stevedennisS 1 Reply Last reply Reply Quote 0
      • stevedennisS Offline
        stevedennis inedo-engineer @scott.wright_8356
        last edited by

        Hi @scott-wright_8356 ,

        Once connector caching is enabled, the error pattern is not used, so we only have this warning. I added a small change via PG-2726 which will add the connector name. This will appear in the next maintenance release (2024.9), scheduled for this week.

        Removing connector caching should reveal the connector name, so maybe that helps you identify it until then

        Thanks,
        Steve

        1 Reply Last reply Reply Quote 0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        • 1 / 1
        • First post
          Last post
        Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation