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

    Adding a Path in Backend Config

    Scheduled Pinned Locked Moved Cache/Proxy
    4 Posts 3 Posters 71 Views 3 Watching
    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.
    • W Offline
      wifi75
      last edited by

      Hi everyone, I have a 3D printer that displays the camera at this link:
      http://192.168.1.71/webcam/?action=stream

      I created a frontend that responds to my domain by pointing to the camera's IP address.
      Then in the backend I created the following as shown in the picure below:

      39dc8e87-bc99-4fc9-8720-a2b04e17a421-image.png

      Unfortunately, if I type https://3dprinter.miodomio.com, it doesn't work.
      What did I do wrong?

      GertjanG W 2 Replies Last reply Reply Quote 0
      • GertjanG Offline
        Gertjan @wifi75
        last edited by

        @wifi75

        I presume you want to make your camera visible on/from the Internet.
        This means that 'requesting' traffioc comes in on the pfSense WAN interface.
        You added a firewall rule on the pfSense WAN interface permitting this traffic ?

        btw : never used HAproxy myself.

        @wifi75 said in Adding a Path in Backend Config:

        if I type https://3dprinter...

        https ?
        or http ?

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        1 Reply Last reply Reply Quote 0
        • W Offline
          wifi75 @wifi75
          last edited by

          If there's a firewall rule, obviously, from the outside
          I get to https

          U 1 Reply Last reply Reply Quote 0
          • U Offline
            Uglybrian @wifi75
            last edited by Uglybrian

            @wifi75 your table shows port 80, not 443 for https

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