Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. Proxy problem after upgrading to 1.1.5

Proxy problem after upgrading to 1.1.5

Scheduled Pinned Locked Moved Support
4 Posts 2 Posters 8.8k Views
  • 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.
  • J
    J
    Marco Incalcaterra
    wrote on last edited by
    #1

    I have a strange problem since the upgrade to version 1.1.5 (I got this behaviour even with version 1.1.4): all the nodes that are accessed through a node that is used as proxy are unreachable. Just reverting the server to 1.1.3 and all works again. The problem isn't the agent version, I tried 1.1.3, 1.1.4, and 1.1.5.

    No problem to reach the node used as proxy as well as all other nodes that are not behind a proxy.

    Any hint? 😞

    Best regards,
    Marco.

    1 Reply Last reply
    0
    • V
      V
      Victor Kirhenshtein
      wrote on last edited by
      #2

      Hi!

      I'll test it during a day.

      Best regards,
      Victor

      1 Reply Last reply
      0
      • V
        V
        Victor Kirhenshtein
        wrote on last edited by
        #3

        I test it on my system with 1.1.5, and everything works as expected. Could you please send me configs of proxy agent and destination agent? Also, what operating system NetXMS server is running on?

        Best regards,
        Victor

        1 Reply Last reply
        0
        • J
          J
          Marco Incalcaterra
          wrote on last edited by
          #4

          Hi Victor,

          thank you very much for your support, I discovered the problem and I feel really stupid to have abused of your precious time...
          The problem was caused to my change to the external IP address associated to the node used as proxy. I still don't understand why it worked with version 1.1.3: this is a change I did very long time ago  ???

          Best regards,
          Marco

          1 Reply Last reply
          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
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          Powered by NodeBB Contributors
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • Users
          • Groups