It's hard to imagine a modern St. Petersburg resident without a smartphone and constant internet access, especially during rush hour when you need to quickly check your email or read the news. The northern capital's subway, one of the oldest and most beautiful in the world, is now equipped with infrastructure that allows you to stay online even tens of meters underground. Free internet access at stations and in underground passages is a lifesaver for those looking to save mobile data or improve connection quality in densely populated tunnels.
However, connecting to the city's "Wifi Metro Spb" (or "Free Metro") network isn't always smooth and may require passengers to have some knowledge of their device's settings. Technical specifications of the equipment, periodic security protocol updates, and the specifics of mobile operators' operations can create situations where automatic authorization fails. In this article, we'll examine the steps for various operating systems in detail and explore why. authorization page may not appear, and we will consider methods for bypassing typical errors.
It's important to understand that signal quality and connection speed directly depend on the number of simultaneously connected users and the current load on base stations. During peak hours, speeds may drop, and the login process may take longer than usual. However, knowing the correct algorithms will allow you to minimize wait times and guarantee access to the global network while you're in the concourses or waiting on the platform.
Finding and selecting the right network to connect to
The first and most obvious step is to find the available signal in your device's settings. The St. Petersburg metro uses several access point names (SSIDs), which can vary depending on the specific line or the year the equipment was installed. Most often, you'll see the names Wifi Metro Spb, Free Metro or simply MT_FREEYou must select the network that is marked as open and does not require a password for the initial connection.
After selecting a network, the device will attempt to establish a connection, which can take anywhere from a few seconds to a minute. At this point, the Android or iOS operating system may display a warning stating "Internet is not working" or "Login required." This is normal, as the subway router itself does not provide direct internet access without completing the necessary steps. authorization via the captive portal. This warning cannot be ignored—you must confirm your desire to remain connected to this network.
⚠️ Warning: Be extremely cautious when connecting to networks with similar names, containing typos, or extra characters (e.g., "Wifi_Metro_Spb_Free"). Attackers can create fake access points to intercept data. The official metro network does not require a phone number or password before accessing the welcome page.
If the automatic pop-up window doesn't appear immediately after connecting, don't panic. Often, your browser blocks pop-ups, or the login page simply hangs in the background. In this case, you should manually open any browser (Safari, Chrome, Yandex) and try accessing any website, for example, ya.ru or google.comThis action will redirect you to the provider's gateway, where you will be required to agree to the terms of use.
Authorization algorithm on Android devices
Owners of Android smartphones face the greatest variety of system behavior scenarios when connecting to public Wi-Fi. Mechanism Captive Portal DetectionThe built-in operating system is designed to automatically open the login window, but different shells (MIUI, OneUI, ColorOS) may behave differently. If the window doesn't appear, try manually entering the gateway IP address, commonly used by ISPs, into the browser's address bar: 1.1.1.1 or http://neiv.fi.
The registration process usually requires entering a mobile phone number, which receives an SMS with a confirmation code, or using an account Government servicesThis is a standard identification procedure mandated by Russian law. After entering the code from the SMS, a connection is established, and you gain internet access for a specified period (usually 1-2 hours), after which the procedure may need to be repeated.
☑️ Android Connection Checklist
It's worth noting that some antivirus apps or VPN services running in the background may block redirection to the login page. It's recommended to temporarily disable them before attempting to log in. VPN and any applications that monitor network traffic. It's also a good idea to check whether the "Use encrypted DNS" option is enabled in your Wi-Fi settings, as this may prevent the captive portal from working properly.
Connection details on iPhone and iPad (iOS)
Apple devices are known for their strict security policies, which can sometimes create additional difficulties when connecting to public networks. In iOS, the login portal detection mechanism works quite reliably, but if the authorization window doesn't appear, the system may simply display "No internet connection" under the network name. In this case, you need to go to Settings → Wi-Fi, click the blue information icon (the letter "i" in a circle) next to the network name and make sure the "Auto-connect" switch is active.
A common problem on iPhones is pop-up blocking in Safari. If redirection doesn't occur, go to Settings → Safari and check if a content blocker is enabled. You can also force the login window to appear by going to http://captive.apple.com — This is a special test address that Apple uses to check for the presence of a captive portal.
An important aspect for iOS users is the feature Private Wi-Fi Address (Private Wi-Fi address). This changes your device's MAC address for each network, which increases privacy, but may cause conflicts with ISP authentication systems that bind sessions to devices. If you can't log in, try disabling this feature for your subway network: in the settings for the specific Wi-Fi network, turn off the "Private Wi-Fi address" toggle switch and reconnect.
What should I do if Safari says "Weak security"?
Modern versions of iOS warn that the network doesn't use WPA3 encryption. This is normal for public open networks (Open Networks), as traffic is encrypted at the HTTPS protocol level within the browser. You can safely ignore this warning unless you're transmitting sensitive banking information.
Troubleshooting the automatic login window
The most common situation is when you have a Wi-Fi connection but the login page doesn't load. This could be caused by your browser attempting to use a secure connection (HTTPS) for the start page, while the portal only supports HTTP. In modern browsers (Chrome, Safari), this can be resolved by attempting to access the site without encryption, for example, by entering [https://en.wikipedia.org/wiki/Login_page_id] in the address bar. http://8.8.8.8 or http://192.168.1.1.
Another possible cause is an overflowing DNS cache. Your phone "remembers" old routes and refuses to request new ones. In this case, an effective solution is to switch your smartphone to airplane mode for 10-15 seconds and then back. This completely resets the network modules and forces the device to re-request the IP address and gateway settings from the metro access point.
If all else fails, you can use specialized Wi-Fi management apps with a built-in "Login Helper" or similar feature. These utilities can force requests that trigger the login window. However, remember to be safe: only install trusted apps from official stores. Google Play or App Store.
Table of common errors and how to fix them
To quickly diagnose connection issues, it's helpful to use the summary table, which describes typical symptoms and solutions. Please note that some errors may not be related to your device, but to temporary issues on the provider's end.
| Symptom / Error | Probable cause | Solution method |
|---|---|---|
| "Connected, no internet access" | Authorization failed | Open your browser and go to http://neiv.fi |
| The login window does not open. | DNS blocking or cache | Change DNS to 8.8.8.8 or clear cache |
| I haven't received an SMS with the code. | Problems with the operator or gateway | Try logging in through Gosuslugi or later. |
| Constant disconnection | Weak signal or overload | Move closer to the access point (antenna) |
| Error "Unable to connect" | IP or saved settings conflict | Delete the network (Forget the network) and reconnect |
An error related to the inability to obtain an IP address deserves special attention. If the connection status shows "Obtaining IP address..." followed by a refusal, this means the address pool on this access point is exhausted or the DHCP server has failed. In this case, the only solution is to wait (5-10 minutes) or move to a different train car or part of the station with a different access point.
APN and DNS settings for stable operation
For advanced users who frequently use public Wi-Fi, manual DNS configuration can be useful. The standard DNS servers of the subway provider are sometimes slow or do not process requests correctly. In the Wi-Fi settings (under "IP Settings" -> "Static" or "Manual"), you can enter public DNS addresses, such as those from Google (8.8.8.8) or Cloudflare (1.1.1.1). This often speeds up the opening of the login start page.
APN (Access Point Name) settings apply to mobile internet (3G/4G/5G) and don't directly affect Wi-Fi. However, if you have mobile internet enabled, your phone may attempt to use it to test the connection, ignoring Wi-Fi. It's recommended to completely disable SIM card data when using the subway network.
⚠️ Warning: Changing DNS settings to static values may cause some local services or applications that rely on your operator's geolocation to not work. After leaving the metro, we recommend returning your DNS settings to "Automatic."
Security Considerations When Using Public Wi-Fi
When using open networks, you should be aware of the risks. Traffic on public Wi-Fi in the metro is typically unencrypted between your device and the router. This means that, theoretically, an attacker on the same network could intercept your data if you transmit it unencrypted. That's why highly not recommended Do not perform banking transactions or enter passwords for important resources until you are sure that the connection is secure (HTTPS).
For maximum security, experts recommend using a VPN service immediately after successfully logging in. This will create a secure tunnel to the VPN provider's server, and all your traffic will be encrypted. Even if someone tries to intercept your packets, they'll only see a jumble of characters. Both paid and free solutions are popular in St. Petersburg, but the latter should be approached with caution.
Frequently Asked Questions (FAQ)
How long does the Wi-Fi connection last in the metro?
An authorization session typically lasts between 1 and 2 hours. After this time, the system may require you to re-enter the code from the SMS. At some stations, this time may be limited to 30 minutes, depending on network load.
Do I need to register again at each station?
No, the metro network is unified. If you've logged in at one station (for example, Nevsky Prospekt), then when you transfer to another (for example, Technological Institute), you should be connected automatically, without having to re-enter your code, until your session expires.
Does Wi-Fi work in the metro cars themselves?
Currently, Wi-Fi coverage is limited to vestibules and platforms. In the tunnels and cars of moving trains, the signal is unreliable or absent altogether, as the equipment is designed for fixed access points rather than high-speed roaming.
Is it possible to watch videos (YouTube, TikTok) via metro Wi-Fi?
Yes, the bandwidth is usually sufficient for watching HD video. However, during peak hours, when hundreds of people are connected to a single access point, the speed may drop, and the video will buffer.
What should I do if I haven't received an SMS with a code?
Try an alternative login method - through the system Government services (If this option is available on the login page). You can also wait 5-10 minutes and try requesting the code again. If the issue is widespread, your service provider or authentication gateway may be undergoing temporary maintenance.