Canada Servers for IVPN has been renamed.
Closed this issue · 2 comments
Hi,
IVPN seems to be switching the naming of their servers for Toronto.
2024-03-18T11:49:35-04:00 INFO [storage] merging by most recent 17820 hardcoded servers and 17820 servers read from /gluetun/servers.json
2024-03-18T11:49:35-04:00 ERROR VPN settings: provider settings: server selection: for VPN service provider ivpn: the hostname specified is not valid: value is not one of the possible choices: value ca-on1.wg.ivpn.net, choices available are at1.gw.ivpn.net, at1.wg.ivpn.net, au-nsw1.gw.ivpn.net, au-nsw1.wg.ivpn.net, au-nsw2.gw.ivpn.net, au-nsw2.wg.ivpn.net, be1.gw.ivpn.net, be1.wg.ivpn.net, bg1.gw.ivpn.net, bg1.wg.ivpn.net, br1.gw.ivpn.net, br1.wg.ivpn.net, ca-qc1.gw.ivpn.net, ca-qc1.wg.ivpn.net, ca01.wg.ivpn.net, ca1.gw.ivpn.net, ca1.wg.ivpn.net, ca2.gw.ivpn.net, ca2.wg.ivpn.net, ch01.wg.ivpn.net, ch1.gw.ivpn.net, ch1.wg.ivpn.net, ch3.gw.ivpn.net, ch3.wg.ivpn.net, cz1.gw.ivpn.net, cz1.wg.ivpn.net, de01.wg.ivpn.net, de1.gw.ivpn.net, de1.wg.ivpn.net, de2.gw.ivpn.net, de2.wg.ivpn.net, dk1.gw.ivpn.net, dk1.wg.ivpn.net, es1.gw.ivpn.net, es1.wg.ivpn.net, fi1.gw.ivpn.net, fi1.wg.ivpn.net, fr1.gw.ivpn.net, fr1.wg.ivpn.net, gb-man1.gw.ivpn.net, gb-man1.wg.ivpn.net, gb01.wg.ivpn.net, gb1.gw.ivpn.net, gb1.wg.ivpn.net, gb2.gw.ivpn.net, gb2.wg.ivpn.net, hk1.gw.ivpn.net, hk1.wg.ivpn.net, hk2.gw.ivpn.net, hk2.wg.ivpn.net, hk3.gw.ivpn.net, hk3.wg.ivpn.net, hu1.gw.ivpn.net, hu1.wg.ivpn.net, il1.gw.ivpn.net, il1.wg.ivpn.net, is1.gw.ivpn.net, is1.wg.ivpn.net, it01.wg.ivpn.net, it1.gw.ivpn.net, it1.wg.ivpn.net, jp1.gw.ivpn.net, jp1.wg.ivpn.net, jp2.gw.ivpn.net, jp2.wg.ivpn.net, lu1.gw.ivpn.net, lu1.wg.ivpn.net, my1.gw.ivpn.net, my1.wg.ivpn.net, nl1.wg.ivpn.net, nl3.gw.ivpn.net, nl3.wg.ivpn.net, nl4.gw.ivpn.net, nl4.wg.ivpn.net, nl5.gw.ivpn.net, nl5.wg.ivpn.net, nl6.gw.ivpn.net, nl6.wg.ivpn.net, nl7.gw.ivpn.net, nl7.wg.ivpn.net, nl8.gw.ivpn.net, nl8.wg.ivpn.net, no1.gw.ivpn.net, no1.wg.ivpn.net, pl1.gw.ivpn.net, pl1.wg.ivpn.net, pt1.gw.ivpn.net, pt1.wg.ivpn.net, ro1.gw.ivpn.net, ro1.wg.ivpn.net, rs1.gw.ivpn.net, rs1.wg.ivpn.net, se01.wg.ivpn.net, se1.gw.ivpn.net, se1.wg.ivpn.net, sg01.wg.ivpn.net, sg1.gw.ivpn.net, sg1.wg.ivpn.net, sk1.gw.ivpn.net, sk1.wg.ivpn.net, tw1.gw.ivpn.net, tw1.wg.ivpn.net, ua1.gw.ivpn.net, ua1.wg.ivpn.net, us-az1.gw.ivpn.net, us-az1.wg.ivpn.net, us-ca01.wg.ivpn.net, us-ca1.gw.ivpn.net, us-ca1.wg.ivpn.net, us-ca2.gw.ivpn.net, us-ca2.wg.ivpn.net, us-ca3.gw.ivpn.net, us-ca3.wg.ivpn.net, us-ca4.gw.ivpn.net, us-ca4.wg.ivpn.net, us-fl1.gw.ivpn.net, us-fl1.wg.ivpn.net, us-ga01.wg.ivpn.net, us-ga1.gw.ivpn.net, us-ga1.wg.ivpn.net, us-ga2.gw.ivpn.net, us-ga2.wg.ivpn.net, us-il01.wg.ivpn.net, us-il1.gw.ivpn.net, us-il1.wg.ivpn.net, us-il2.gw.ivpn.net, us-il2.wg.ivpn.net, us-nj3.gw.ivpn.net, us-nj3.wg.ivpn.net, us-nj4.gw.ivpn.net, us-nj4.wg.ivpn.net, us-nv1.gw.ivpn.net, us-nv1.wg.ivpn.net, us-ny1.wg.ivpn.net, us-ny2.gw.ivpn.net, us-ny2.wg.ivpn.net, us-ny3.gw.ivpn.net, us-ny3.wg.ivpn.net, us-tx01.wg.ivpn.net, us-tx1.gw.ivpn.net, us-tx1.wg.ivpn.net, us-tx2.gw.ivpn.net, us-tx2.wg.ivpn.net, us-ut1.gw.ivpn.net, us-ut1.wg.ivpn.net, us-va1.gw.ivpn.net, us-va1.wg.ivpn.net, us-wa2.gw.ivpn.net, us-wa2.wg.ivpn.net
Update your servers data, see https://github.com/qdm12/gluetun-wiki/blob/main/setup/servers.md#update-the-vpn-servers-list
Those hostnames show up when I update my data locally.
Closed issues are NOT monitored, so commenting here will NOT be seen by the maintainer.
If you think this is still unresolved and have more information to bring, please create another issue.
This is an automated comment setup because @qdm12 is the sole maintainer of this project
which became too popular to monitor closed issues for additional comments.