Photo Supreme Manuals
All manuals

Photo Supreme documentation

Search all manuals

Enter at least two characters.
    Manual contents
    1. Introduction
    2. Choose Who Should Be Able to Connect
    3. Prepare the Computer and Catalog
    4. Configure and Start the Embedded Server
    5. Configure the PSO Pages
    6. Router and Host-Firewall Rules
    7. Use an HTTPS Reverse Proxy
    8. Browser Origins and CORS
    9. Security and Privacy Checks
    10. Verify the Setup
    11. Troubleshooting

    Getting Started with Photo Supreme's Integrated HTTP Server

    Troubleshooting

    SymptomWhat to check
    No START button or settings unavailableMain-administrator sign-in, edition/license, and whether the server is already running. Stop it before editing settings.
    Connection refused or timeoutPhoto Supreme still open, server started, correct port, address/DNS, host firewall, and any intended proxy/router rules. Check for another process using the port.
    Works on the server but not on another computerlocalhost still in either API field, wrong LAN address, guest Wi-Fi isolation, or firewall scope.
    Page loads, but sign-in failsapi.url, /auth/* routing, ordinary catalog credentials, certificate trust, and CORS. Do not send database-login credentials to the browser.
    Sign-in works, but thumbnails or previews failapi.thumbsUrl, media API routing, catalog file access, and mixed-content restrictions.
    The API address appears to end in /api/api/...Remove /api from the base address in config.json.
    Browser reports a CORS errorActual page origin versus Domain Name Origin, preflight handling, duplicate CORS headers from two layers, and the underlying response. An unreachable backend can look like a CORS problem.
    HTTPS page calls HTTP or private addressesCorrect both API fields to the browser-facing HTTPS endpoint, then reload.
    Settings seem ignoredWrong web root edited, malformed JSON, cached page/config, or a proxy sending index.htm instead of config.json.
    Proxy returns 502 or 504Backend stopped/unreachable, wrong upstream port or protocol, backend TLS validation, or an unsuitable timeout.
    Shared page fails on refresh or direct-image URL is missingSPA fallback and /directimage/* rewrite rules. Compare with the supplied IIS routing rules or the Caddy example.
    Local-network-only or IP-limit rejectionCheck the edition and the application's returned message. Do not bypass edition restrictions with a proxy.

    Configuration templates and external references were reviewed on October 17,

    1. Proxy setup is environment-specific; validate it with your administrator

    before exposing a private catalog to the Internet.