Meta tags:
Headings (most frequently used words):
configuration, apache, caddy, reverse, proxy, setup, server, folder, nginx, v2, navigation, related, topics, quick, search, donate, support,
Text of the page (most frequently used words):
the (16), syncthing (12), #configuration (10), you (9), server (8), proxy (7), localhost (7), 8384 (7), your (7), http (6), reverse (5), setup (5), gui (5), https (4), apache (4), web (4), following (4), host (4), proxy_set_header (4), location (4), folder (3), this (3), access (3), none (3), forwarded (3), existing (3), site (3), security (2), principles (2), profiling (2), usage (2), documentation (2), file (2), files (2), authentication (2), command (2), for (2), page (2), rewriterule (2), rewritecond (2), add (2), same (2), have (2), caddy (2), 600s (2), proto (2), all (2), module (2), headers (2), pass (2), want (2), share (2), with (2), donate, support, quick, search, next, previous, overview, related, topics, specifications, development, automatic, crash, reporting, community, contributions, starting, automatically, custom, upgrade, relay, discovery, versioning, ignoring, ssh, tunneling, using, proxies, relaying, firewall, untrusted, encrypted, devices, understanding, synchronization, prometheus, style, metrics, tuning, ldap, listen, address, introducer, types, advanced, versions, releases, faq, line, operation, introduction, navigation, written, version, gf020590, edit, github, method, also, redirects, prevent, opening, unencrypted, env, server_name, request_uri, 301, rewriteengine, below, webroot, which, should, redirect, webui, produce, behaviour, above, htaccess, don, might, try, technique, handle_path, reverse_proxy, header_up, upstream_hostport, transparent, timeouts, read, write, header, proxy_send_timeout, proxy_read_timeout, proxy_pass, scheme, proxy_add_x_forwarded_for, remote_addr, real, nginx, set, expr, request_scheme, granted, require, requestheader, proxypassreverse, proxypass, then, may, httpd, first, execute, enable, and, proxy_http, a2enmod, use, examples, hosted, ssl, certificates, need, port, 443, but, already, website, device, especially, useful, allows, requests, through, another, program, will, make, look, like, within,
Text of the page (random words):
reverse proxy setup syncthing documentation reverse proxy setup a reverse proxy allows you to pass requests through your web server to another site or program the reverse proxy will make it look like syncthing s gui is a page within your existing site this is especially useful if you need to access the gui on port 80 or 443 but you already host a website on the same device you want to share ssl certificates with an existing site you want to share authentication with an existing setup server configuration if you have access to your web server s configuration use the following examples to pass the location syncthing on your web server to syncthing s gui hosted on localhost 8384 apache first of all execute the following command to enable the apache http proxy module and the headers module a2enmod proxy_http headers then you may add the following to your apache httpd configuration location syncthing proxypass http localhost 8384 proxypassreverse http localhost 8384 requestheader set x forwarded proto expr request_scheme require all granted location nginx location syncthing proxy_set_header host host proxy_set_header x real ip remote_addr proxy_set_header x forwarded for proxy_add_x_forwarded_for proxy_set_header x forwarded proto scheme proxy_pass http localhost 8384 proxy_read_timeout 600s proxy_send_timeout 600s caddy proxy syncthing localhost 8384 transparent timeouts read none write none header none caddy v2 handle_path syncthing reverse_proxy http localhost 8384 header_up host upstream_hostport folder configuration if you don t have access to your web server configuration files you might try the following technique apache add the configuration below to a htaccess file in the folder of your webroot which should redirect to the webui syncthing to produce the same behaviour as above rewriteengine on rewritecond https on rewritecond env https on rewriterule https server_name request_uri r 301 l rewriterule http localhost 8384 1 p this method also redirects to https to prevent opening the gui unencrypted edit this page on github version v2 1 0 26 gf020590 written for v2 1 0 navigation introduction usage command line operation faq versions releases configuration advanced configuration folder types introducer configuration the gui listen address ldap authentication configuration tuning prometheus style metrics understanding synchronization untrusted encrypted devices firewall setup relaying using proxies ssh tunneling ignoring files file versioning syncthing discovery server syncthing relay server custom upgrade server starting syncthing automatically community contributions profiling reverse proxy setup security principles automatic crash reporting development specifications related topics documentation overview usage previous profiling next security principles quick search donate support
|