We had the same issue. We solved putting a reverse proxy just for the webhooks. In this way, nothing is exposed public but just the necessary for the webhook
A tiny machine with Nginx using proxy_pass directive does the trick. Cheers, Gianluca On Wed, 17 Jun 2020, 06:18 Harald Dunkel, <[email protected]> wrote: > Hi folks, > > how can I obfuscate Jenkins' login page? I don't want everybody > to know that its a Jenkins prior to login. > > IMHO its an unlucky design decision to run the user web interface > and the webhook interface on the same port number. I wouldn't have > to open the user web interface to the world outside, if not for the > webhooks coming from google cloud. Or did I miss something here? > > > Every helpful comment is highly appreciated > > Harri > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/baa73c8c-49ea-7625-debe-6fa814e026af%40afaics.de > . > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPddqDWZpYQV%3DbaE2uVq2Q%3DPtgNduaXVMDXnqFBHYa0o9eATpg%40mail.gmail.com.
