{"id":13836939,"url":"https://github.com/rekby/lets-proxy","last_synced_at":"2025-07-10T16:31:17.272Z","repository":{"id":65932682,"uuid":"73906314","full_name":"rekby/lets-proxy","owner":"rekby","description":"See https://github.com/rekby/lets-proxy2 instead of this. Reverse proxy which automatically obtains TLS certificates from Let's Encrypt.","archived":true,"fork":false,"pushed_at":"2019-04-28T19:16:41.000Z","size":9125,"stargazers_count":151,"open_issues_count":0,"forks_count":21,"subscribers_count":7,"default_branch":"master","last_synced_at":"2024-08-05T15:05:30.701Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":"Go","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/rekby.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE.txt","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2016-11-16T09:50:54.000Z","updated_at":"2024-01-04T16:09:04.000Z","dependencies_parsed_at":"2023-02-16T23:30:37.575Z","dependency_job_id":null,"html_url":"https://github.com/rekby/lets-proxy","commit_stats":null,"previous_names":[],"tags_count":66,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/rekby%2Flets-proxy","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/rekby%2Flets-proxy/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/rekby%2Flets-proxy/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/rekby%2Flets-proxy/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/rekby","download_url":"https://codeload.github.com/rekby/lets-proxy/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":225647988,"owners_count":17502162,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-08-04T15:00:57.722Z","updated_at":"2024-11-20T23:32:00.677Z","avatar_url":"https://github.com/rekby.png","language":"Go","funding_links":[],"categories":["Go"],"sub_categories":[],"readme":"[![Go Report Card](https://goreportcard.com/badge/github.com/rekby/lets-proxy)](https://goreportcard.com/report/github.com/rekby/lets-proxy)\n\nРусскоязычное описание ниже (Russian below).\n\nEnglish description\n===================\nNow this version program support for bugfix, but no active development.\nNew version are in development, welcome to issues: https://github.com/rekby/lets-proxy2\n\nA reverse-proxy server to handle https requests transparently. By default Lets-proxy handles\nhttps requests to port 443 and proxies them as http to port 80 on the same IP address.\n\nLets-proxy adds the http headers, `X-Real-IP` which contains the IP address\nof remote client and, `X-Forwarded-Proto=https`, for https detection. It obtains valid TLS certificates from Let's Encrypt and\nhandles https for free, in an automated way, including certificate renewal, and without warning in browsers.\n\nLets-proxy has a TCP mode, which doesn't parse traffic and proxies it as usual TCP connection without modification.\n\nThe program was created for shared hosting and can handle many thousands of domains per server. It is simple to implement and doesn't need settings to start the program on personal server/vps.\n\nSince lets encrypt disable TLS-SNI validation for create new certificates - lets-proxy need handle http-traffic for directory /.well-known/acme-challenge/ of certificated domain. Now it can proxy by server config or scripts to http://127.0.0.1:4443/.well-known/acme-challenge/ (bind address can be changed by arg --bind-http-validation-to). \n\n[Http-01 validation guide](https://github.com/rekby/lets-proxy/wiki/Proxy-http-01-validation).\n\nQuick start:\n\n    ./lets-proxy or lets-proxy.exe\n    \nInstall for autostart (daemon for linux or windows-service for linux)\n    \n    ./lets-proxy --service-name=lets-proxy --service-action=install\n    lets-proxy.exe --service-name=lets-proxy --service-action=install\n    \n\nRemove from autostart\n\n    ./lets-proxy --service-name=lets-proxy --service-action=uninstall\n    lets-proxy.exe --service-name=lets-proxy --service-action=uninstall\n\nUse --help key for details:\n\n    ./lets-proxy --help or lets-proxy.exe --help\n\n\nРусский (Russian):\n==================\n\nЭта версия поддерживается в части исправления существующих багов, но активно не разрабатывается.\nАктивная разработка ведётся в https://github.com/rekby/lets-proxy2 там можно оставлять все пожелания и замечания.\n\n\nРеверс-прокси сервер для прозрачной обработки https-запросов. Для начала использования достаточно просто запустить его на сервере с \nзапущенным http-сервером. При этом lets-proxy начнёт слушать порт 433 и передавать запросы на порт 80 с тем же IP-адресом.\nК запросу будут добавляться заголовки X-Real-IP с IP-адресом источника запроса и X-Forwarded-Proto=https - для определения\nчто запрос пришел по https. Сертификаты для работы https получаются в реальном времени от letsencrypt.org. Это правильные\n(не самоподписанные) бесплатные сертификаты, которым браузеры доверяют.\n\nЕсть режим tcp-прокси, в этом случае входящий трафик никак не анализируется и не меняется, а просто передается на указанный порт, но\nуже в расшифрованном виде.\n\nПрограмма разрабатывается для использования на виртуальном хостинге и может работать с тысячами доменов на каждом сервере.\nС другой стороны она проста и не требует начальных настроек для запуска на персональном сервере.\n\nС момента отключения Lets encrypt варианта проверки домена через tls-sni для работы lets-proxy требуется обработка в lets-proxy проверочного http-трафика. Через настройки сервера или скрипты нужно передавать запросы к папке \"/.well-known/acme-challenge/\" обслуживаемых доменов на внутренний обработчик валидации lets-proxy: http://127.0.0.1:4443/.well-known/acme-challenge/ (адрес привязки может быть изменен параметром --bind-http-validation-to).\n\n[Инструкция по настройке проверок http-01](https://github.com/rekby/lets-proxy/wiki/Proxy-http-01-validation).\n\nБыстрый старт:\n\n    ./lets-proxy или lets-proxy.exe\n\nУстановить в автозапуск (демон в linux, служба в windows)\n    \n    ./lets-proxy --service-name=lets-proxy --service-action=install\n    lets-proxy.exe --service-name=lets-proxy --service-action=install\n    \n\nУдалить из автозапуска\n\n    ./lets-proxy --service-name=lets-proxy --service-action=uninstall\n    lets-proxy.exe --service-name=lets-proxy --service-action=uninstall\n\nДля получения подробной справки воспользуйтесь --help:\n\n    ./lets-proxy --help or lets-proxy.exe --help\n\n\nUsed libraries (alphabet ordered):\n==================================\n\n* http://github.com/hashicorp/golang-lru - memory cache\n* http://github.com/hlandau/acme/acmeapi - used for work with lets encrypt\n* http://github.com/kardianos/service - working as service, especially for windows.\n* http://github.com/miekg/dns - direct dns requests, IDN decode\n* http://github.com/sevlyar/go-daemon - unix daemonize\n* http://github.com/Sirupsen/logrus - logging\n* http://gopkg.in/natefinch/lumberjack.v2 - log rotate\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Frekby%2Flets-proxy","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Frekby%2Flets-proxy","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Frekby%2Flets-proxy/lists"}