[0.15.40] No IPv6 on auth web servers

[JulienCC]

Hello,

I'm trying to run a headless server on an IPv6 only machine.
The server stops because of :

0.528 Info HttpSharedState.cpp:44: Downloading https://auth.factorio.com/generate-server-padlock-2
0.654 code:7, 7; Couldn't connect to server

It seems that auth.factorio.com doesn't provide any AAAA record.
Is it possible to add IPv6 support to the auth server ?

I could use a tunnel or a proxy but that would be great if IPv6 could work out of the box.

PS : I'm not looking for workarounds, just reporting my situation.

[HanziQ]

Unfortunately no, at least for now. The authentication server runs on Heroku, which doesn't support IPv6 for some reason. But I am in the middle of moving some parts of our infrastructure to different providers, so I could do that also for the auth server, in the future. No promises.

[JulienCC]

Thanks for the reply, at least I know you are aware of the situation.

The authentication server runs on Heroku, which doesn't support IPv6 for some reason

Heroku uses AWS, probably they always did. But AWS started to provide IPv6 quite recently, especially on certain of their products.
That could be a reason. I'll ask them.

[JulienCC]

I asked for a roadmap or anything, here is the answer :

Hello,

We don't currently have any plans to support IPv6, to keep up to date with product announcements and new features, please subscribe to our Blog and Changelog

Best,
Tim

There's nothing more I can do on my side.

[HanziQ]

Fortunately, the auth server is a fairly easy service, so it won't be too difficult to migrate.

[Gachl]

Sorry for necroing this thread but is there any update to this?
The headless server supports IPv6 since 0.12 but the auth.factorio.com gateway doesn't, is adding full IPv6 support still on the tasklist?

[movax20h]

Yeah. I still see this. The 1) DNS points only to hosts with IPv4 addresses (via herokudns):

Code: Select all

$ host auth.factorio.com
auth.factorio.com is an alias for perpendicular-shark-yujs6bj61byj1q191y5wyd47.herokudns.com.
perpendicular-shark-yujs6bj61byj1q191y5wyd47.herokudns.com has address 34.233.35.85
perpendicular-shark-yujs6bj61byj1q191y5wyd47.herokudns.com has address 35.168.165.30
perpendicular-shark-yujs6bj61byj1q191y5wyd47.herokudns.com has address 34.206.126.139
perpendicular-shark-yujs6bj61byj1q191y5wyd47.herokudns.com has address 34.227.155.170
perpendicular-shark-yujs6bj61byj1q191y5wyd47.herokudns.com has address 52.54.249.116
perpendicular-shark-yujs6bj61byj1q191y5wyd47.herokudns.com has address 34.230.145.192
perpendicular-shark-yujs6bj61byj1q191y5wyd47.herokudns.com has address 35.169.40.78
perpendicular-shark-yujs6bj61byj1q191y5wyd47.herokudns.com has address 52.73.84.118

I would appreciate this being fixed. Not sure how easy or hard would it be, but better do it sooner than later. I guess some scripts, filters, and log parser tools / audit database might require some testing first for it to support both. It might not be as easy as listening on IPv6 and IPv4 bind sockets, and exposing it via DNS.

I suspect the connection logic itself in factorial client should mostly work without issues. And hopefully defaults to using OS preferences in regards to IPv4 vs IPv6.

I would appreciate this being implemented.

I noticed some pieces you host on AWS, which does support IPv6 very well actually for quite some time now. Alternatively contacting somebody in sales / support and explicitly poking them to support IPv6 soon, would be a good option.