This then inspects the header for the originating domain (or subdomain) and it then upgrades the headers and points each request to a local network IP, which is of course the IP of the correct server for that domain or subdomain. The internet facing router has a portforward rule to send all port 80 requests to 192.168.1.15 which is the NGINX server. I use the nameserver zone editor to carve up subdomains on my main website which allows me to host different services for my own use (I have a search engine, a wiki, a website, a nextcloud server and so on). The setup is that I have one internet facing IP and I host quite a few sites (and other things - email etc). I have set my instance of this project behind an NGINX reverse proxy. Wsd-00015-00023 18:05:26.212475 WRN FileServerRequestHandler: File not found: Invalid URI request. Wsd-00015-00023 18:05:26.018280 WRN FileServerRequestHandler: File not found: Invalid URI request. Wsd-00015-00023 18:05:24.813640 WRN FileServerRequestHandler: File not found: Invalid URI request. Wsd-00015-00023 18:05:24.620217 WRN FileServerRequestHandler: File not found: Invalid URI request. Wsd-00015-00023 18:05:16.647657 WRN FileServerRequestHandler: File not found: Invalid URI request. Wsd-00015-00023 18:05:16.420838 WRN FileServerRequestHandler: File not found: Invalid URI request.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |