It’s unclear to me what will happen to our v2 gateways after december 1st.
We currently have ~20 gateways on v2, routing traffic from our v3 end devices to our TTI stack. But as these gateways are spread out over different countries it is difficult to access them for re-configuration.
Will they still keep forwarding to v3 through the packet broker after december 1st?
Yes, but this is a bonus with an indeterminate timescale for support - deeply unlikely to be a forever option - so don’t hang about with migration as soon as you reasonably can.
As @descartes already wrote, this is indeed temporary, so you will have to reconfigure your gateways.
If you need to physically access the gateways to do this, please take that opportunity to also set up secure remote access so that you reconfigure and upgrade your gateways in the future without having to visit them.
And your solution for those of us without the wifi code/claim code for remote TTIG’s to hand is…? 
!
Surely start point should be if I am the ‘owner’ (and sole collaborator) in V2 then there is no obvious reason why I should not continue to be the ‘owner/sole collaborator’ in V3!.. In otherwords if the migration is being done from the same account surely there should be no issue - perhaps a validation email to the address associated with the account to say something like ‘an attempt is being made to migrate “gateway name/gateway eui” from V2 to V3 do you accept this? click here link 1 to accept click here link 2 to reject, if no response seen within 24hrs the migration will be rejected’ or something similar?
Good plan - could knock up a one-shot database thing in a few hours - but not let you test …
When I finally migrated a Kerlink using the Semtech UDP protocol a week ago, basically all I did on that gateway was this from the documentation:
If you are using a Semtech UDP Packet Forwarder, change the
server_addressin yourglobal_conf.jsontoeu1.cloud.thethings.network
This used to refer to router.eu.thethings.network. I’m sure it has been considered, so what would break if somewhere after December 1st any remaining V2 gateway would just be migrated from V2 Console to V3 Console, and that old domain name would just become an alias for the new one?
This has come up earlier, but I don’t think it was answered:
There is an potential issue with certificates used by mqtts connected gateways. For UDP gateways there wouldn’t be issues.
Ah, I guess there is nothing like SNI for MQTT, or maybe not all clients support that if it exists? But then, that could be solved with an extra IP address, serving one certificate per IP address? As long as ports don’t change, I’d assume that would work, if wanted.
(Lacking a true community in Haarlem I was very much tempted not to bother migrating that specific gateway, thinking it would need a USB-triggered firmware upgrade. But I learned some beekeepers are using it, and in the end one of your posts convinced me it would/should be easy.)
The incident on our status page was just updated with new information. The first post in this topic has been updated accordingly.
The incident on our status page was just updated with new information. The first post in this topic has been updated accordingly.
R.I.P. good old v.2 — we´ve had many nice times, lots of fun, some stressful nights and days but at all today is the time to leave and say good bye ! – thanks to the TTI Team for giving the v.3 TTS CE to us — and another big thankyou to all the volunteers here in the forum and in slack !!!
how can we send downlink messages via the console until dec 7 if you’ve moved the link to the console from the picker? https://console.cloud.thethings.network/ WHERE’S THE LINK TO THE OLD CONSOLE? : )
Try e.g. The Things Network for gateways, https://v2console.thethingsnetwork.org for the top level, The Things Network for applications etc.
jeff, you save my Week-end with the link you share! 
Because I am very late for the migration…
Today we started auto-migrating TTIGs from The Things Network V2 to The Things Stack Community Edition. See Auto-Migration of The Things Indoor Gateways for details.
Links are not working. They redirect to V3.
Is it possible to get on V2 console just to see what devices I have and which were alive just before shutdown? Some users of the sensors can’t live without everyday dose of the enviromental measurements and I would like to try to move that to V3. The devices use ABP. Is this OK with V3?
If you read just three posts up you will see the link.
But you may well be too late.
It looks like the bot forgot to post a reply. Here’s the latest update:
We’re still cleaning up servers behind the scenes, but all public V2 APIs have been shut down.
So I’m afraid you’re too late, @s54mtb.
OK, thanks. I was trying in past several times without success. Looks it’s time to clean crap from the field and recycle to some new devices 