Does that happen with other browsers?

My first thought is a TLS issue... there's a big enough mismatch in security settings that Verizon's front-end is not even trying. I would want to find out what certificate is being presented and make sure it's trust chain is intact (ie. I have any and all intermediate and root CA certs in my cert store) and make sure they aren't using either too old of a cipher (SSL or a really weak algo) or too new (maybe locked to TLS 1.2 and your Firefox isn't negotiating that correctly). You can use the 'openssl' command-line tool to help figure this out.

Hi Edgewater, I'm not familiar with Verizon's web mail interface. Are you getting a tab that just has a white background and "502- bad gateway" in black text, or is there more to it? Is it when you launch a message from your Inbox or can you not get anything useful from the site?

If you are using an old bookmark to get to your mail: try going through the front page in case there is a "failure to redirect" with the old address. http://www.verizon.com/?lid=//global//residential

And if you haven't already:

When you have a problem with one particular site, a good "first thing to try" is clearing your Firefox cache and deleting your saved cookies for the site.

(1) Clear Firefox's Cache

See: How to clear the Firefox cache

If you have a large hard drive, this might take a few minutes. If you do not see the number going down on the page, you can reload it using Ctrl+r to check progress.

(2) Remove the site's cookies (save any pending work first). While viewing a page on the site, try either:

• right-click (on Mac Ctrl+click) a blank area of the page and choose View Page Info > Security > "View Cookies"
• (menu bar) Tools > Page Info > Security > "View Cookies"
• click the padlock or "i" icon in the address bar, then the ">" button, then More Information, and finally the "View Cookies" button

In the dialog that opens, the current site should be pre-filled in the search box at the top of the dialog so you can remove that site's cookies individually.

Then try reloading the page. Does that help?

Hi jnojr, is this available for Windows 10?

You can use the 'openssl' command-line tool to help figure this out.

Could be handy to learn, but I'm sure a tutorial will be needed.

I'm not a Windows guy, but:

http://gnuwin32.sourceforge.net/packages/openssl.htm

Assuming it works under Windows like a "real" OS (sorry, couldn't resist!), you'll see something like:

[joliver@neetdev08 ~]$ openssl s_client -connect www.google.com:443 CONNECTED(00000003) depth=3 C = US, O = Equifax, OU = Equifax Secure Certificate Authority verify return:1 depth=2 C = US, O = GeoTrust Inc., CN = GeoTrust Global CA verify return:1 depth=1 C = US, O = Google Inc, CN = Google Internet Authority G2 verify return:1 depth=0 C = US, ST = California, L = Mountain View, O = Google Inc, CN = www.google.com verify return:1 --- Certificate chain

0 s:/C=US/ST=California/L=Mountain View/O=Google Inc/CN=www.google.com
  i:/C=US/O=Google Inc/CN=Google Internet Authority G2
1 s:/C=US/O=Google Inc/CN=Google Internet Authority G2
  i:/C=US/O=GeoTrust Inc./CN=GeoTrust Global CA
2 s:/C=US/O=GeoTrust Inc./CN=GeoTrust Global CA
  i:/C=US/O=Equifax/OU=Equifax Secure Certificate Authority

--- Server certificate

<SNIPPED>

subject=/C=US/ST=California/L=Mountain View/O=Google Inc/CN=www.google.com issuer=/C=US/O=Google Inc/CN=Google Internet Authority G2 --- No client certificate CA names sent Server Temp Key: ECDH, prime256v1, 256 bits --- SSL handshake has read 3727 bytes and written 373 bytes --- New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES128-GCM-SHA256 Server public key is 2048 bit Secure Renegotiation IS supported Compression: NONE Expansion: NONE SSL-Session:

   Protocol  : TLSv1.2
   Cipher    : ECDHE-RSA-AES128-GCM-SHA256
   Session-ID: 59EDDB44D4299E8715BFC31E5AEF6FF44E9EDAF3E225B2DF8E8CD04565517733
   Session-ID-ctx: 
   Master-Key: 60919DE7248763922E462D665E53BBBBA44963CFD6C57CC46FBD7A89B85B479CB9FE07437C848054C0954CA9900BFF0D
   Key-Arg   : None
   Krb5 Principal: None
   PSK identity: None
   PSK identity hint: None
   TLS session ticket lifetime hint: 100800 (seconds)
   TLS session ticket:
   0000 - 5d 17 47 c4 74 b4 05 02-be 8f 4d 91 be 99 c3 42   ].G.t.....M....B
   0010 - 65 a9 76 f9 b1 0c df c8-d1 11 a6 35 4d 14 53 5c   e.v........5M.S\
   0020 - e5 61 67 d5 8f 5b dd 5b-95 07 5b 1e 6d c2 c8 d7   .ag..[.[..[.m...
   0030 - af 42 2d ae d7 c0 22 2b-14 86 4a 59 2e 50 a8 59   .B-..."+..JY.P.Y
   0040 - 1a 7a e0 3a ab a9 f5 ac-90 ef f8 31 eb 68 1e 1e   .z.:.......1.h..
   0050 - 26 7b 49 2c 27 0f 67 6f-82 37 95 8c 29 e4 d5 17   &{I,'.go.7..)...
   0060 - 10 b5 6d 3d ec 9e 4b 8d-7c 2f ff 32 3d 97 b5 d4   ..m=..K.|/.2=...
   0070 - d0 3e 69 a7 16 c0 8f b6-d3 aa 9e 67 b6 03 4a 55   .>i........g..JU
   0080 - 60 c7 e2 87 ce a7 b3 ff-94 7c 29 63 4e 7c 5c fd   `........|)cN|\.
   0090 - 88 2b a1 6d 4f d1 6d 4b-5e de 5b 38 d7 5d 9e a8   .+.mO.mK^.[8.]..
   00a0 - ad 37 84 70                                       .7.p

   Start Time: 1482173327
   Timeout   : 300 (sec)
   Verify return code: 0 (ok)

--- ^C