[GH-ISSUE #941] how would you exposé whoogle or similar behind kemp loadmaster #585

New issue

Closed

opened 2026-02-25 20:36:05 +03:00 by kerem · 1 comment

kerem commented

2026-02-25 20:36:05 +03:00

Owner

Originally created by @candyman4092 on GitHub (Jan 27, 2023).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/941

seams like must things that are https work fine i can set them up behind my domain and can use them outside my network with https://blah.example.com but if i try to set up a http ip through loadmaster says its up but i can not connect to it through the internet via my domain sorry im very new to loadmaster and reverse proxies so please be gentle

Originally created by @candyman4092 on GitHub (Jan 27, 2023). Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/941 seams like must things that are https work fine i can set them up behind my domain and can use them outside my network with https://blah.example.com but if i try to set up a http ip through loadmaster says its up but i can not connect to it through the internet via my domain sorry im very new to loadmaster and reverse proxies so please be gentle

kerem

2026-02-25 20:36:05 +03:00

closed this issue
added the
question
label

kerem commented

2026-02-25 20:36:05 +03:00

Author

Owner

@benbusby commented on GitHub (Jan 30, 2023):

I don't have any experience with loadmaster, but it sounds like you need to configure a domain and certificate for your whoogle instance before you can access it. The typical approach is to use LetsEncrypt for that. If you already have other services behind your own domain, you could use something like "whoogle.yourdomain.com" point your ip:port to that subdomain and then generate a certificate for it.

I'll convert this issue into a discussion in case anyone else has any ideas or already has experience with loadmaster.

@benbusby commented on GitHub (Jan 30, 2023): I don't have any experience with loadmaster, but it sounds like you need to configure a domain and certificate for your whoogle instance before you can access it. The typical approach is to use [LetsEncrypt](https://letsencrypt.org/getting-started/) for that. If you already have other services behind your own domain, you could use something like "whoogle.yourdomain.com" point your ip:port to that subdomain and then generate a certificate for it. I'll convert this issue into a discussion in case anyone else has any ideas or already has experience with loadmaster.