Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add IPv6
listen
directives to Nginx configuration templatesI believe that agent services don't listen on IPv6 by default. This PR attempts to fix this issue by adding IPv6 specific lines to the Nginx config templates.
Deployment notes
agent setup nginx
seems to be needed to update the configuration on all server types, unless another event updates it.AAAA records should be added after making the server accept IPv6 requests.
References
https://serverfault.com/questions/638367/do-you-need-separate-ipv4-and-ipv6-listen-directives-in-nginx/638370#638370
https://serverfault.com/questions/512054/globally-setting-ipv6only-off/512213#512213
https://stackoverflow.com/questions/40189084/what-is-ipv6-for-localhost-and-0-0-0-0/40189197#40189197
https://docs.aws.amazon.com/en_us/lightsail/latest/userguide/amazon-lightsail-configure-ipv6-on-nginx.html#configure-ipv6-nginx