facebook

Alternate Web Mappings for Reverse Proxy Servers

  1. Secure Delivery Center
  2.  > 
  3. Getting Help
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #682032 Reply

    d0d00n
    Participant

    Hi,

    We are on version v5.5.0v201912

    I am trying to configure my Secure Delivery Centre (server.internal.tld:1305) to use our reverse proxy (proxy.external.tld/sdc). Our Admin app points straight to server.internal.tld:1305. From there, I go to Configure Web Mappings as per https://www.genuitec.com/docs/sdc/advanced-administration/setting-alternate-web-mappings-reverse-proxy-servers

    I set the End-User URLs to follow the existing patterns

    Client web services: https://proxy.external.tld/sdc/ws/user/
    Secure marketplaces: https://proxy.external.tld/sdc/marketplace/
    Update sites: https://proxy.external.tld/sdc/site/
    End-user help: https://proxy.external.tld/sdc/help/ (which matches the existing link on the end-user portal, but contains the script
    window location set to learning-center script that sends me over to learning-center.)

    When I click on Set Mappings, it is happy. But it doesn’t appear to take. The Help link at the top still points to http://server.internal.tld:1305/help and the login form submission points to http://server.internal.tld:1305/ws/portalLogin.

    I have tried restarting deliveryCenterServer but the values remain the same.

    I thought perhaps the Delivery Portal URLs need to be changed as well, so we set both:

    Main web portal: https://proxy.external.tld/sdc/
    End-user only portal: https://proxy.external.tld/sdc/

    However, when we click Set Mappings, we get an error

    “Incorrect mapping: first line received was (!doctype html) (html) (head) (meta charset=”utf-8″) (… for https://proxy.external.tld/sdc/checkMapping”

    The unusual thing about that error is that SDC appears to return the same result with the proxy or directly. I have attached curl responses as a separate file.

    So I am not sure what the expectation is for the checkMapping to succeed.

    Any help with getting the URLs to function correctly on the portal or getting pass the checkMapping for the Delivery Portal URLs would be appreciated.

    Thanks so much for your time and attention.

    Cheers,

    Don

    #682033 Reply

    d0d00n
    Participant

    My curl output contained html could not be uploaded, but essentially it’s the Loading… page containing the webmappings.js, styles, polyfills, scripts, main bundles.

    #682099 Reply

    ignaciom
    Moderator

    Hey,

    Please try the following:

    Main web portal: https://proxy.external.tld/sdc/full/portal
    End-user only portal: https://proxy.external.tld/sdc/portal/end

    Then you can have a redirect when the path is just ^/sdc/$ to redirecto to /sdc/full/portal

    Let us know how this works for you.

    Best Regards
    Ignacio

    #682131 Reply

    d0d00n
    Participant

    Hi Ignacio,

    Thanks for the suggestion. Putting in that end-user only portal URL worked for me.

    However, the login URL and help URLs appear to use http://server.internal.tld:1305 still, whether I fill in the End-User URLs or not.

    Do you have any other suggestions to perform as a sanity check?

    Thanks,

    Don

    #682132 Reply

    ignaciom
    Moderator

    Hey,

    It will be nice if we could move this conversation to the ticket system, we need to look at some of the files on your system and it does not look like the forums allow to upload files.

    If you look on the following file ${delivery_hub_install_dir}/Data Files/system-config/server-runtime.xml you will find the web-mappings xml element it should look something like this:

       <web-mappings updated-at="1411666955505">
            <mapping type="PORTALFULL" uri="https://${your.host.name}/sdc"/>
            <mapping type="WSEND" uri="https://${your.host.name}/sdc/end/user"/>
            <mapping type="MARKET" uri="https://${your.host.name}/sdc/marketplace/"/>
            <mapping type="DLSITE" uri="https://${your.host.name}/sdc/site"/>
            <mapping type="DLADMIN" uri="https://${your.host.name}/sdc/dl/admin/"/>
            <mapping type="WSADMIN" uri="https://${your.host.name}/sdc/ws/admin/"/>
            <mapping type="WSBUILD" uri="https://${your.host.name}/sdc/ws/build/"/>
        </web-mappings>

    If not please edit manually, stop your Delivery Hub and delete the directory “${delivery_hub_install_dir}/Data Files/artifacts/admin-console”. After this start your Delivery Hub.

    Please also share your apache/nginx configuration.

    Best Regards
    Ignacio

    • This reply was modified 2 years, 3 months ago by ignaciom.
Viewing 5 posts - 1 through 5 (of 5 total)
Reply To: Alternate Web Mappings for Reverse Proxy Servers

You must be logged in to post in the forum log in