Page 1 of 2 12 LastLast
Results 1 to 10 of 13
  1. #1
    Untanglit rcaballero's Avatar
    Join Date
    Sep 2008
    Posts
    20

    Default Failed to connect to Untangle [cmd.untangle.com]

    Guys,

    I'm having the triangle notification that says "Failed to connect to Untangle [cmd.untangle.com]" after upgrading to 9.4.0 build. I upgraded via the upgrade button at the Config tab. I am not sure what this means as the UT box is working fine right now. I just want to fix this before something comes up.

    Thanks!

  2. #2
    Untangle Ninja
    WebFooL's Avatar
    Join Date
    Jan 2009
    Location
    Sweden (Eskilstuna)
    Posts
    5,273

    Default

    Hi rcaballero,

    I have seen the same thing.

    But i think that it just some parts of there new Central management that they are working on.

    But only the devs can answer what it is really is used for :-)

  3. #3
    Untangle Ninja sky-knight's Avatar
    Join Date
    Apr 2008
    Location
    Phoenix, AZ
    Posts
    26,387

    Default

    I'd get on the physical console and make sure Untangle can browse untangle.com.

    If you've got ssh, you can ping untangle.com from there as well. Those errors usually simply mean Untangle is having a hard time phoning home, which is required for many of Untangle's features. As to what cmd.Untangle.com does... I'm not qualified to answer, can't even venture a guess.
    Rob Sandling, BS:SWE, MCP
    NexgenAppliances.com
    Phone: 866-794-8879 x201
    Email: support@nexgenappliances.com

  4. #4
    Untangle Junkie dmorris's Avatar
    Join Date
    Nov 2006
    Location
    San Carlos, CA
    Posts
    17,747

    Default

    http://wiki.untangle.com/index.php/A...trative_Alerts

    It means it can't connect to cmd.untangle.com
    Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself.
    If you need Untangle support please call or email support@untangle.com

  5. #5
    Untanglit
    Join Date
    Jul 2012
    Posts
    24

    Default Agreed

    Quote Originally Posted by dmorris View Post
    http://wiki.untangle.com/index.php/A...trative_Alerts

    It means it can't connect to cmd.untangle.com

    Having the same issue here. Untangle works with full function. This error message is the only indication that something is going on. Am able to connection test to that site without issues (though it doesn't respond to ping requests; something I assume that is turned off on their end).

  6. #6
    Untangler jcoffin's Avatar
    Join Date
    Aug 2008
    Location
    Lake Tahoe
    Posts
    9,804

    Default

    Ping is not the full story. I suggest using tcpdump from the Untangle terminal console and see if you are getting a proper http response from cmd.untangle.com.
    Attention: Support and help on the Untangle Forums is provided by
    volunteers and community members like yourself.
    If you need Untangle support please call or email support@untangle.com

  7. #7
    Newbie
    Join Date
    Mar 2013
    Posts
    1

    Default

    I also upgraded to 9.4.0 and am getting the same error. Has anyone had success fixing this yet?

  8. #8
    Untangler jcoffin's Avatar
    Join Date
    Aug 2008
    Location
    Lake Tahoe
    Posts
    9,804

    Default

    There is no universal fix. You need to determine why your external interface can't reach cmd.untangle.com.
    Attention: Support and help on the Untangle Forums is provided by
    volunteers and community members like yourself.
    If you need Untangle support please call or email support@untangle.com

  9. #9
    Untangle Ninja jcoehoorn's Avatar
    Join Date
    Mar 2010
    Location
    York, NE
    Posts
    1,891

    Default

    I want to revive this, because I haven't been able to get to cmd.untangle.com for some time, and it has nothing to do with my network. Here's the trace route:

    Code:
    C:\Users\jcoehoor>tracert cmd.untangle.com
    
    Tracing route to cmd.untangle.com [74.123.28.85]
    over a maximum of 30 hops:
    
      1     1 ms    <1 ms    <1 ms  10.1.1.1
      2    <1 ms    <1 ms    <1 ms  untangle.york.edu [10.1.1.5]
      3    75 ms    83 ms   103 ms  rrcs-76-79-19-33.west.biz.rr.com [76.79.19.33]
      4    49 ms    34 ms    26 ms  tge3-2.swrdne01-rtr1.neb.rr.com [76.85.221.85]
      5     2 ms     2 ms     2 ms  tge4-3-0.lnclne00-mx42.neb.rr.com [76.85.221.81]
    
      6    67 ms    90 ms   108 ms  ae9.chcgileq-rtr1.kc.rr.com [76.85.220.133]
      7    25 ms    22 ms    22 ms  ae-4-0.cr0.chi10.tbone.rr.com [66.109.6.100]
      8    52 ms    72 ms    46 ms  107.14.17.192
      9    33 ms    21 ms    21 ms  te0-2-0-7.ccr22.ord03.atlas.cogentco.com [154.54
    .11.145]
     10    57 ms    49 ms    56 ms  te0-3-0-5.ccr21.ord01.atlas.cogentco.com [154.54
    .1.1]
     11   235 ms   211 ms   222 ms  te0-3-0-0.ccr21.mci01.atlas.cogentco.com [154.54
    .7.185]
     12   176 ms   178 ms   187 ms  te0-3-0-3.ccr21.sfo01.atlas.cogentco.com [154.54
    .24.109]
     13   411 ms   373 ms   204 ms  te2-3.ccr02.sfo04.atlas.cogentco.com [154.54.27.
    38]
     14   157 ms   201 ms   197 ms  38.99.32.203
     15     *        *        *     Request timed out.
     16     *        *        *     Request timed out.
     17     *        *        *     Request timed out.
     18     *        *        *     Request timed out.
     19     *        *        *     Request timed out.
     20     *        *        *     Request timed out.
     21     *        *        *     Request timed out.
     22     *        *        *     Request timed out.
     23     *        *        *     Request timed out.
     24     *        *        *     Request timed out.
     25     *        *        *     Request timed out.
     26     *        *        *     Request timed out.
     27     *        *        *     Request timed out.
     28     *        *        *     Request timed out.
     29     *
    Note that it doesn't fail until it's already in San Francisco... looks like a peering problem of some kind with whoever it is that Cogent is handing off to. Nothing I could possibly do on my end to fix it, and I'd bet this is happening to most anyone running through Time Warner or Cogent networks.

    I'd really love to make this go away, because it takes what could be a really awesome feature (administrative alerts) and makes it next to worthless, but it's not worth my time anymore to look at the icon.

    Hmm... Another side tidbit: I may need to call Time Warner, because our contract with them stipulates less than 50 milliseconds of latency, and they're up over 70 on the best response here.
    Last edited by jcoehoorn; 03-18-2013 at 01:47 PM.
    Five time Microsoft ASP.Net MVP managing a Lenovo RD330 / E5-2420 / 16GB with Untangle 16.4.1 to protect 500Mbits for ~450 residential college students and associated staff and faculty

  10. #10
    Untangle Junkie dmorris's Avatar
    Join Date
    Nov 2006
    Location
    San Carlos, CA
    Posts
    17,747

    Default

    Failure to run traceroute to that host has nothing to do with it - traceroute is blocked to that host.

    It needs to be able to connect and maintain a TCP SSL connection to cmd.untangle.com.
    If it can not it will throw this alert.
    Last edited by dmorris; 03-18-2013 at 03:15 PM.
    Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself.
    If you need Untangle support please call or email support@untangle.com

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

SEO by vBSEO 3.6.0 PL2