Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    HTTP ACCESS PROBLEM

    Scheduled Pinned Locked Moved OpenVPN
    3 Posts 2 Posters 2.0k 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.
    • O
      onkeldave83
      last edited by

      hello

      my openvpn strctur is:

      intranet (lan)  –- squid cache proxy --- havp proxy --- intranet (lan)

      the vpn client can ping every machine in network and can access https sites in network, and can access vnc connections or remote desktop cpnnections, BUT

      he cant access normal http protocol and i dont know why???????????

      to add, i have squid proxy listen on 127.0.0.1 and havp proxy on lan interface with parent proxy squid.
      https access - no http ???? why??? firewall is open to all to test ;)

      i can access throw vpn:
      all servers ping and filesharing but not apache http
      vpn client can surf throw internet on other site throw squid and havp and proxy filter

      outbound rule vpn: vpn source to network destination
      outbound rule lan: vpn source to network destination
      squid is on port 3333
      and havp on 8080
      port redirect from lan from 80 to 8080
      and that is in my opinion the problem to access f.e. http:\192.168.10.6:80   because i can access 192168.10.6:3000 (its a tool for network stats)
      how can i fix this

      please can someone help me why i cant access http protocol

      1 Reply Last reply Reply Quote 0
      • O
        onkeldave83
        last edited by

        what have i basic set, that i can access http over openvpn?

        redirect gateway or not?

        1 Reply Last reply Reply Quote 0
        • Cry HavokC
          Cry Havok
          last edited by

          If it can't access HTTP, but can access other protocols, then it's either a proxy configuration setting on the client that's wrong or a configuration issue with the proxy server(s).

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.