How and when to use LOCAL_NETWORK_ALLOWLIST?

[jchonig]

This is briefly mentioned in the release nodes, but you can expand on it's use?

I run gogs in a docker container and have a couple repos that send webhooks.

Thanks.

Jeff

[unknwon]

When you want to migrate repositories or send webhooks from/to a local network address (not a public IP address on internet). If everything is working from your perspective, there is no need to take action.

To use it:

[security]
# specific network address, separated by commas, no port needed
LOCAL_NETWORK_ALLOWLIST = bitbucket.local, sourcegraph.test

[unknwon]

0.12.10 is currently planned to be released on July 30th (not a commitment 🤫).

[kankan-k2]

I have a similar requirement where I want localhost to used for a webhook. I am running gogs inside a docker container. How do I use this inside a docker container?
I created a custom/config/app.ini file inside the /app/gogs/ folder and put just this:
/app/gogs # cat custom/conf/app.ini
[security]
# specific network address, separated by commas, no port needed
LOCAL_NETWORK_ALLOWLIST = *

But it doesn't work.

I am using the latest label of the gogs docker image

[kankan-k2]

actually solved it.
based on logs in the docker, custom config is picked up from /data/gogs/conf/app.ini. Added this option/parameter there and restarted the container. gogs seemed to have picked up the change and allowed me to create the webhook using localhost.

[kankan-k2]

one problem which I found while trying to use localhost (or 127.0.0.1 or 0.0.0.0). gogs is unable to send/make requests to localhosts. here is a sample response:
Delivery: Post "http://localhost:8890/monitor": dial tcp [::1]:8890: connect: connection refused

But if I replace the localhost with the actual IP of the localhost/my system (the local home network IP or if connected to VPN, then the IP provided by that VPN service), then gogs is able to make the HTTP requests.

Not sure if this is a bug or an intended behavior.

[unknwon]

Delivery: Post "http://localhost:8890/monitor": dial tcp [::1]:8890: connect: connection refused

Judging based on the error message, I think it is an intended behavior.