ipv6only by default

[pniederlag]

I spent some time to analyse why my nginx would not be working as intented. In the end I found the default configuration, which enables ipv6only support in nginx to be the reason.

To me it would make sense to deliver more sensible defaults as ipv6only is not the regular default mode of operation.

I have spotted #86 which helped me to solve my problems

[drybjed]

Hi. This is a very popular issue, I think that lack of proper documentation for debops.nginx explaining how the service configuration is laid out is the problem. Currently debops.nginx lacks documentation, and not sure when it will be written, but I'll definitely get to it at some point.

The default mode of operation for nginx is with ipv6only=on, that's presumably why the default server shipped in Debian uses separate network sockets for IPv4 and IPv6 protocols. I've based the debops.nginx defaults similar to how it's explained in this blog, so that nginx uses only one network bind for both networks. An alternative is to use two binds, I imagine that there are pros and cons to both approaches as well as fans of either solution. Changing the default in debops.nginx to use separate sockets could happen, but it needs extensive testing to make sure nothing will be broken, and I have other stuff to worry about at the moment.

[pniederlag]

You are doin an incredible job, big thx for your comitment. Just wanted to give you some feedback:

Default user experience of nginx in debian: "works"
Default user exeperience of nginx role in debops: "was painful to get working"

Overall user experience of debops: Incredible awesome!!!!!

[drybjed]

@pniederlag Glad you like it. :) I suspect that you only use debops.nginx by itself? If you would try setting up a host with roles that use debops.nginx, for example debops.owncloud or debops.gitlab, you would probably see that it works without issues. Also, DebOps is designed to be appled to a completely clean, base Debian install - if you tried it with something else, you might have some issues. Can you tell me more about how you use it? Maybe we could find a solution that way.

[carlalexander]

I know I ran into issues as well with it. That's why WordPress forces IPv4
at the moment. That said, I was asked about IPv6 last week so I'll be
taking a look at it again soonish.
On Mon, May 23, 2016 at 9:39 AM Maciej Delmanowski [email protected]
wrote:

@pniederlag https://github.com/pniederlag Glad you like it. :) I
suspect that you only use debops.nginx by itself? If you would try
setting up a host with roles that use debops.nginx, for example
debops.owncloud or debops.gitlab, you would probably see that it works
without issues. Also, DebOps is designed to be appled to a completely
clean, base Debian install - if you tried it with something else, you might
have some issues. Can you tell me more about how you use it? Maybe we could
find a solution that way.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#119 (comment)

[pniederlag]

@drybjed I am rolling out debops on two hosts. So, I am using the debops shell-wrapper, effectivly applying the common.yml playbook (just learned on the bootstrap playbook after it was to late).

I do manage custom vhosts setups for individual (php based) web projects, mostly running TYPO3 CMS, maybe evolving to a role some time later....

[rochecompaan]

For what its worth, this issue bit me too. Given how many people trip over this, it doesn't seem like the best choice to have ipv6only=on as the default.