Skip to content
This repository has been archived by the owner on Jan 13, 2022. It is now read-only.

Does not support systems without an IPv4-resolvable FQDN #53

Open
fredemmott opened this issue Oct 13, 2015 · 2 comments
Open

Does not support systems without an IPv4-resolvable FQDN #53

fredemmott opened this issue Oct 13, 2015 · 2 comments

Comments

@fredemmott
Copy link
Contributor

main reason is that nginx listens on 0.0.0.0:80 but not [::0]:80

@fredemmott
Copy link
Contributor Author

(workaround is to add fqdn to /etc/hosts as 127.0.0.something)

@swtaarrs
Copy link

I tried a few variants of adding [::]: in front of __HTTP_PORT__ in the nginx config file but they all failed with:

siege aborted due to excessive socket failure; you
can change the failure threshold in $HOME/.siegerc

So maybe siege needs to be made ipv6-aware or something?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants