I've been traveling to Europe for two weeks. I've used international roaming with my T-Mobile One account. My device is an iPhone 7, which I've occasionally tethered to a MacBook Pro laptop. I noticed the following:
- The network name displayed was "T-Mobile LTE" in Amsterdam and "TELEKOM.RO" (followed by one of "E", "3G", or "LTE" in Romania depending on location). On rare occasions, the provider in Romania switched to "orange 3G".
- With signal, everything on the phone works as expected: http (insecure) and https (secure) browsing, gmail (SSL/TLS connection over port 993), apps.
- On the laptop using tethering however, https does not work - it always times out. And it's not sometimes and it's not because of some slow connectivity; I could verify speed of connection readily on the phone itself. It always times out, and on all https sites (google, apple, yahoo, wikipedia, ibm... you name it; most sites in broad usage today are only usable with https). Also, gmail (same SSL/TLS port 993) also does not work. Somewhat surprisingly, ssh on port 22 works swimmingly.
Back in the USA, I tried the same setup and everything (including https tethering) works fine.
I called and first spoke to a CSR who forwarded me to a tech expert. The latter said it's the first time he hears about it, but that it's technically not difficult for a given provider (or partner/subsidiary) to specifically restrict https tethering. He hypothesized that that might be a way for roaming partners to reduce roaming usage.
This was quite the bummer seeing I've changed providers specifically because of being able to work while traveling.
Has anyone experienced this problem in these countries or others? Is there a palatable workaround? Thanks!