WebMail not keeping me signed in

Paul-K
Contributor III

It seems that the backend to the "Keep me signed in" checkbox isn't working properly since about Monday or Tuesday of this week I now have to sign in about 4 or 6 times a day.

I'm using an up to date Edge browser "Version 114.0.1823.58 (Official build) (64-bit)".

Any ideas?

Tnx...Paul...

 

 

0 57 8,077
57 REPLIES 57

Sorry to hear that. Mine is fixed. I think you should try calling Bell again.

 

The sign-on box for Email no longer automatically adds the email address. Have to type it in every time.

It seems that the old problem of Bell not keeping you logged in to your email (even though the keep me logged in box is ticked) has started happening again. It was an issue with the change-over to the new email system but was finally fixed. Now (August 2024) I am experiencing the same issue, not quite as bad as it only happens every few days. Has anyone else having this issue? I hesitate calling Bell Support as they are useless.

Good Day.

Which browser are you using to access your webmail? Have you checked your Privacy settings in your browser? If not, then you should so. In Microsoft Edge, Select > the 3-dots top right corner of your web bowser. Scroll down & Select > Settings. Scroll down again & Select > Privacy, search & services. On the right side of the page is a section called: Clear Browsing Data. Within this section there are two subsections:

  1. Clear browser data now > Choose what ot clear now
  2. Choose what to clear every time you close the browse

Within each of these subsections, there are options for what to save or close when the Edge browser is open or after you are finished & have closed the Edge browser.

If you are using Google Chrome or another compatible browser, the process is very similar. Look for the 3-dots, Settings & a similar Privacy section to save or delete your stored browser data.

Take care.

I am a Community All-Star and customer. I'm here to help by sharing my knowledge and experience. My views on Bell and the Community Forum are my own and not the views of Bell or any of its affiliates.

Once again the issue of staying logged into Bell mail has reappeared, but this time with an additional problem.. When I try to access my email it asks for my password even though I have ticked off the box to stay logged in. Now, however it does not recognize my password. I have to go to the Bell app and change my password. It lets me change it to the same password that I was already using. This is a nuisance.

Looks like this problem is now re-occurring. I keep having to sign in (not every time like before) but frequently.

Pj
Contributor III

Yep, i've been having this problem again too - computer, tablet and phone!!

Hi there @Pj @evermore 
We wanted to check in to see if you're still experiencing this issue?
If so, can you share where / how you accessing your Bell email and which devices (make and model)?
Have you tried logging out of your email on all devices?
Have you tried clearing your browser cache, cookies & history if accessing on a web-browser?
Looking forward to hearing back.

Pj
Contributor III

this was happening on all devices - phone, PC and Android tablet
all seems to be working as it should now, although I did have to set up the 2 factor verification

thanks

DixieL
Contributor

This is happening again! And now that we have the additional security step of having to enter a verification code, logging in to Webmail is getting to be a real pain. Anyone else having this problem? Only started @a few weeks ago!!

Hey @DixieL 

Thanks for posting in the Bell community.

Can you share which web browser you are using? Are the cookies/caches set to be cleared every time your browser is closed? To start, we recommend checking the settings and ensure you choose not to clear the history when you close the browser.

Let us know if that works,

@BellPatricia 

 

My browser is Safari on my iPad. and no, I do not have the clear cache history checked off under my browser settings.

Appears every time Bell makes a change to their webmail, this happens! Recent  change of adding secondary security of now having us enter a verification code seems to have triggered this nuisance again.