Force HTTPS at the web-server or reverse-proxy edge, not inside ownCloud alone. Install a valid certificate for the public hostname, make the HTTPS endpoint work, then redirect the port-80 virtual host to that HTTPS URL with a permanent 301. If TLS ends at a proxy, also tell ownCloud which proxy is trusted and that the original request protocol was HTTPS.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
Why HTTPS must be enforced at the edge
Plain HTTP allows traffic to be read or altered between a client and your server. ownCloud’s security guidance warns that an unencrypted connection can expose the installation to man-in-the-middle attacks and interception of user data and passwords. A redirect is therefore the final step of an HTTPS deployment, not a substitute for a working certificate: the server must already be able to complete a TLS handshake on port 443 before port 80 is redirected.
As an Amazon Associate I earn from qualifying purchases.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →The edge component can be Apache or Nginx on the ownCloud host, or a separate reverse proxy such as HAProxy or a managed proxy. Whichever component receives the public request owns the certificate, the HTTP-to-HTTPS redirect, and the forwarding headers that tell ownCloud how the request arrived.
Choose where TLS terminates
Decide this before editing ownCloud. The correct configuration depends on which service first receives connections from the internet.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
| Termination point | Operational owner | What ownCloud must know | Main operational concern |
|---|---|---|---|
| Apache or Nginx on the ownCloud host | The server administrator manages the certificate, HTTPS virtual host, and redirect. | Usually no protocol override is needed because the web server passes an HTTPS request directly to ownCloud. | Certificate renewal and port-80/443 firewall rules remain on the same host. |
| Separate Nginx, HAProxy, Cloudflare, or another reverse proxy | The proxy administrator manages TLS and forwards requests to the private ownCloud service. | Add the proxy address to trusted_proxies; use overwriteprotocol, overwritehost, or overwritewebroot only when ownCloud misdetects those values. |
Forwarded headers and client-IP handling must be correct; trusting the wrong sender allows address spoofing. |
In either design, point DNS at the public edge, ensure ports 80 and 443 reach that edge, and use the same public hostname everywhere. A proxy should forward the original host and protocol rather than replacing them with an internal name.
Prerequisites before changing redirects
- A DNS record for the public ownCloud hostname, such as
cloud.example.com, pointing to the public server or proxy. - Port 443 reachable at the intended edge and a valid TLS certificate covering that hostname.
- Port 80 reachable long enough to answer the redirect. If it is blocked, users cannot automatically upgrade old HTTP bookmarks.
- Administrative access to the edge web server or proxy and to ownCloud’s
config/config.phpwhen a proxy is involved. - A maintenance or rollback plan. Permanent redirects can be cached by browsers and intermediaries, so validate HTTPS before enabling the 301 in production.
Apache: serve HTTPS, then redirect port 80
1. Install and verify the certificate
Configure the Apache TLS virtual host for the public hostname and install the certificate and private key supplied by your certificate authority. Confirm that a browser can open https://cloud.example.com/, that the certificate matches the hostname, and that ownCloud loads through the public URL before touching the port-80 virtual host.
2. Add the permanent HTTP redirect
Use a separate port-80 virtual host whose only job is to redirect every path to the HTTPS origin:
<VirtualHost *:80>
ServerName cloud.example.com
Redirect permanent / https://cloud.example.com/
</VirtualHost>The Redirect permanent directive returns HTTP status 301. Keep the destination hostname identical to the certificate name; changing hostnames during the redirect can create login, cookie, and WebDAV problems.
3. Reload Apache and test both schemes
Reload Apache using the service-management method for your operating system, then request an HTTP URL and inspect the response headers. A correct result is a 301 whose Location header begins with https://cloud.example.com/. Follow that location and verify that the final response is served over TLS. Test a nested path as well as the root so that the redirect does not silently drop path information.
curl -I http://cloud.example.com/
curl -I https://cloud.example.com/Do not add HSTS until these checks, certificate renewal checks, and application tests succeed.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
Reverse-proxy TLS termination
How the protocol gets lost
When a proxy accepts HTTPS and forwards ordinary HTTP on a private network, ownCloud may see the internal hop rather than the original secure request. It can then generate http:// links, issue redirects to an internal hostname, or mark secure cookies incorrectly. The fix has two parts: trust only the proxy that is allowed to assert forwarded headers, and override only the value ownCloud still detects incorrectly.
Trust the proxy address
Add the proxy’s private address to trusted_proxies. The address in this example is illustrative; replace it with the actual source address that connects to the ownCloud application:
'trusted_proxies' => ['10.0.0.10'],Do not trust an entire internet-facing network unless every address in that range is under your control. ownCloud gives trusted proxies special treatment, and an incorrect trust list can let a client spoof its apparent IP address through forged forwarding headers. If the proxy uses more than one fixed source address, list each known address explicitly according to your deployment.
Tell ownCloud that the public request was HTTPS
In config/config.php, set the protocol override when TLS terminates before ownCloud:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
'overwriteprotocol' => 'https',ownCloud documents http and https as the accepted protocol values. Use the override when the proxy is correctly forwarding requests but ownCloud still believes the original scheme was HTTP.
Correct the public host or web root only when needed
If links contain the proxy’s internal hostname, set the public host. If the application is published below a path rather than at the domain root, set the public web root. A complete example combining the four settings is:
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
'trusted_proxies' => ['10.0.0.10'],
'overwriteprotocol' => 'https',
'overwritehost' => 'cloud.example.com',
'overwritewebroot' => '/',Do not copy every override automatically. Start with trusted_proxies and overwriteprotocol; add overwritehost or overwritewebroot only if generated URLs demonstrate that those values are being misdetected. An incorrect web-root override can break static assets and WebDAV paths.
Preserve the original host and protocol at the proxy
Configure the proxy to pass the public Host and the original HTTPS indication to the upstream. The exact directive names differ between Nginx, HAProxy, Cloudflare, and other products, but the requirement is the same: ownCloud must receive trustworthy information about the external hostname and scheme. Ensure the proxy’s source IP is the value placed in trusted_proxies, not an address a client can select.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsDocker deployments: keep the public URL consistent
In the official Docker setup, the public domain and overwrite behavior can be supplied through environment variables. The important names are:
OWNCLOUD_DOMAINfor the public hostname.OWNCLOUD_TRUSTED_DOMAINSfor hostnames that clients are allowed to use.OWNCLOUD_OVERWRITE_CLI_URLfor the HTTPS URL used by command-line and background operations.- Environment-variable settings for overwrite protocol, overwrite host, overwrite web root, and trusted proxies when your image and deployment expose them.
Set the public HTTPS hostname consistently in the proxy configuration, container environment, and ownCloud trusted-domain list. A mismatch can produce a valid browser login while cron jobs, sharing links, or WebDAV clients receive an internal name or an HTTP URL.
Pin the container to an explicit image version rather than latest. An explicit tag makes upgrades deliberate and gives you a known configuration to roll back if a proxy or environment-variable behavior changes. After changing environment variables, recreate the container using your normal deployment process so the running process actually receives the new values.
Validate the complete request path
Testing only the landing page is insufficient. Work through the public hostname from an external network and check each of these cases:
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
- Request
http://cloud.example.com/and confirm one 301 response to the corresponding HTTPS URL. - Open the HTTPS URL directly and verify the certificate name, validity dates, and absence of browser mixed-content warnings.
- Sign in and sign out. Check that the browser remains on the public HTTPS hostname and does not switch to an internal address.
- Create or open a sharing link and inspect its scheme and hostname.
- Connect a WebDAV client over the public HTTPS endpoint. Confirm that authentication, directory listing, uploads, and downloads work.
- Run a cron or background job that generates URLs, then inspect its output for the public HTTPS origin.
- Check a representative deep path, not just the root, to catch a faulty web-root override or redirect that strips paths.
Use browser developer tools or a header request to identify the first response that changes the scheme or hostname. The component that emits that response is where the correction belongs.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshooting common failures
Redirect loop between HTTP and HTTPS
A loop usually means the proxy terminates TLS but the upstream request is interpreted as HTTP, so the application redirects to HTTPS on every hop. Confirm that the proxy forwards the original protocol, that its source address is in trusted_proxies, and that overwriteprotocol is set to https when necessary. Make sure the proxy itself is not redirecting an already-HTTPS request back to its HTTP listener.
HTTPS works, but links still say HTTP
Check the generated link’s hostname and scheme separately. If only the scheme is wrong, use overwriteprotocol. If the hostname is internal, use overwritehost with the public name. If links contain the wrong path prefix, correct overwritewebroot. Apply the smallest change, then regenerate a link and test again.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Users see the proxy’s internal hostname
Ensure the proxy preserves the external Host header and that overwritehost matches the certificate name. Also check that Docker’s domain setting and trusted-domain setting use the same public hostname. A certificate for the public name cannot make an internal name safe; the URL itself must be corrected.
Client IP addresses are incorrect
Review the trusted-proxy list and forwarding chain. Trusting an unverified sender allows clients to claim arbitrary addresses; trusting no proxy can make every user appear to originate from the proxy. List only the fixed proxy addresses that actually connect to ownCloud, then retest access logs and any rate-limiting or audit features that depend on client IP data.
WebDAV or desktop clients fail after the redirect
Verify that the client follows the 301 to the same public hostname and that the certificate chain is trusted by the client operating system. Check deep-path redirects and the web-root setting. If a proxy publishes ownCloud beneath a path, an incorrect overwritewebroot can send collection requests to the wrong location even though the browser home page works.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
HSTS made the site inaccessible
HSTS instructs compatible browsers to use HTTPS automatically and can prevent bypassing a certificate or subdomain problem until the policy expires. Remove or reduce the policy only through a controlled recovery plan; users who have already cached it may continue enforcing HTTPS. This is why HSTS belongs after certificate renewal, proxy forwarding, subdomain coverage, and client testing are proven.
Recommended Free Tools
Add HSTS only after HTTPS is stable
Once the certificate, redirect, generated URLs, WebDAV, sharing, and background jobs are reliable, add an HSTS header on the TLS virtual host or HTTPS proxy. ownCloud’s example is:
Strict-Transport-Security: max-age=15768000; includeSubDomains; preloadmax-age=15768000 is the policy lifetime in seconds. includeSubDomains extends the rule to every subdomain, so use it only when every required subdomain is HTTPS-capable. The preload token signals an intent to participate in browser preload programs; do not treat it as a substitute for validating certificates and redirects. HSTS is stronger than a redirect: a browser that has accepted the policy will refuse HTTP before contacting your server, and an incorrect certificate or HTTP-only subdomain can make access fail.
Certificate renewal and ongoing operations
HTTPS enforcement is a continuing service obligation. Certificate renewal must update the certificate at the component that terminates TLS, whether that is Apache, Nginx, HAProxy, or a managed proxy. After each renewal, test the public hostname from an external network and confirm that the proxy still forwards the expected host and protocol. Keep the port-80 redirect available unless you have a deliberate reason to remove it; it upgrades old bookmarks and clients that still begin with HTTP.
When changing proxies, private addresses, Docker networks, or hostnames, revisit trusted_proxies, the overwrite settings, DNS, and the certificate as one change set. Remove old proxy addresses from the trust list when they are no longer able to connect. If you change the public hostname, obtain a certificate for the new name and update Docker domain variables, trusted domains, generated URL settings, and client configurations together.
A practical rollout order
- Point DNS at the intended public proxy or server and verify that ports 80 and 443 arrive there.
- Install a certificate and make the HTTPS virtual host or proxy work without redirects.
- Confirm that the edge forwards the original public host and protocol to ownCloud.
- Add the permanent port-80 redirect and test both the root and a deep URL.
- If TLS ends at a proxy, add only its known source addresses to
trusted_proxies. - Set
overwriteprotocoltohttpswhen ownCloud still detects HTTP; add host or web-root overrides only when evidence shows they are needed. - For Docker, align the public domain, trusted domains, CLI URL, and overwrite variables, then recreate the container using an explicit image version.
- Test login, sharing links, WebDAV, cron-generated URLs, and client behavior through the public HTTPS hostname.
- Add HSTS after certificate renewal and all required subdomains have been checked.
This sequence keeps the redirect, application URL generation, proxy trust, and browser policy in the correct order: establish secure transport first, teach ownCloud how the public request looked second, and apply irreversible client-side policy last.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
