topic Re: Cannot login in Get Support

Cannot login

joyker — Mon, 25 Jul 2022 15:21:27 GMT

For the first month everything was great! I could login no problem, signed someone up to get rewards ... I could track rewards etc ... NOW? No login at all ... I get this message when I go to selfserve.publicmobile.ca ...

{
  "message":"Request header or cookie too large"
}

Any ideas? I like the price and convenience but this is a major issue for me!

Re: Cannot login

hairbag1 — Mon, 25 Jul 2022 15:23:19 GMT

Try clearing the cache files. Try using incognito or secret mode.

Try a different web browser. Firefox works great for me.

Re: Cannot login

hTideGnow — Mon, 25 Jul 2022 15:25:19 GMT

HI @joyker Look like it could be just cache issue, please try with Incognito mode

Or if you have a laptop/desktop around, try accessing from there

Re: Cannot login

softech — Mon, 25 Jul 2022 15:25:21 GMT

@joyker Try to use Incognito more, or clear cache and reboot the browser. Or try to use a completely different browser (Edge/Firefox/Chrome). Or try on another machine

Re: Cannot login

iliketotalk — Mon, 25 Jul 2022 15:25:36 GMT

@joyker there have been many issues with login since the upgrades try a different device to login, use a different browser in ingognito mode, if problem persists

you will need to open a ticket through Simon to speak to a customer service agent they will help you mention update email for self serve account

Click here if you have issues using Simon , try to pm them here https://productioncommunity.publicmobile.ca/t5/notes/composepage/note-to-user-id/22437 you will get a response from them in your community envelope

Re: Cannot login

joyker — Mon, 25 Jul 2022 15:27:44 GMT

Thanks much for the info ... this is the first interaction in 2 months with someone! I have tried different devices, cleared my cookies etc ... still get the same issue. Simon? It's like going around in circles! If I could login I wouldn't need to submit a ticket ... and you have to be logged in to submit a ticket? Catch 22 for me!!!

Re: Cannot login

hTideGnow — Mon, 25 Jul 2022 15:29:56 GMT

HI @joyker since you tried all these ways, you likely need to open ticket with CS Agent

Yes, the quicker way is to use SIMON/Chatbot to open. No, worry, type exactly what I suggest below and you can open a ticket win 30 seconds (or you can use direct message as well):

at : https://publicmobile.ca/chatbot. Follow this to get to ticket open screen quicker:

First type: "Forgot log in information"
Then Click "Contact Us"
Finally Click "Click here to submit a ticket"
you will then direct to another page to open ticket.

Once ticket is submitted, make sure to check your Community Inbox(top right corner envelope icon) periodically for response from PM's CS Agent

If you have problems submitting a ticket, you can also send a private message to the CS Agent (but this can take longer):

https://productioncommunity.publicmobile.ca/t5/notes/composepage/note-to-user-id/22437

Re: Cannot login

iliketotalk — Mon, 25 Jul 2022 15:32:59 GMT

@joyker try my second suggestion to contact customer service it's easier

try to pm them here https://productioncommunity.publicmobile.ca/t5/notes/composepage/note-to-user-id/22437 you will get a response from them in your community envelope

Re: Cannot login

joyker — Mon, 25 Jul 2022 15:35:11 GMT

Thanks so much for this ... the incgnito suggestion worked for me ... I'll just do that for now but will keep this suggestion in mind ... thanks!

Re: Cannot login

hTideGnow — Mon, 25 Jul 2022 15:56:59 GMT

HI @joyker glad it works.

Yes, the cache is a big enemy to PM site. Always try Incognito mode or other browser if you encounter any problem

Re: Cannot login

newmanwilson — Mon, 10 Oct 2022 18:10:05 GMT

not resolve issue

Re: Cannot login

dabr — Mon, 10 Oct 2022 22:35:52 GMT

~~@joyker~~ @newmanwilson (edit: wrong username tagged) You're unable to login using incognito or private mode? Have you tried using a different browser?

I just tried with Firefox and had no problem logging into the self serve account. Perhaps, there was a temporary website issue when you tried earlier.