03-03-2026 01:13 PM - edited 03-03-2026 01:15 PM
Have received my router and am trying to change the ssid and password before the service goes live (tomorrow). This is a transfer from BT. I plugged in the new router and connected it to my Mac via ethernet cable. I managed to access the router consul by typing in the address in my web browser. I then tried to access "advanced" but the admin password did not give me access - it just hung there with spinning balls. It is definitely the correct password as per the info supplied with the EE router. Any ideas? Is it getting confused withy the BT router which is still connected. Ideally I would like to change ssid and password before putting the EE router into a live environment.
Thank you
Solved! See the answer below or view the solution in context.
03-03-2026 04:03 PM
Thank you for confirming. So it looks like something is wrong with the router? If I cannot change the sussed and password then I do not want it as to move forward by changing the details in all my working wi fi devices would be a nightmare.
03-03-2026 04:05 PM - edited 03-03-2026 04:08 PM
So no way of really knowing as if I cannot change the ssid etc in advance I will not use the router! Interestungkly when I turn the EE router on the flashing light is green but turns to orange flashing when this problem arises.
03-03-2026 04:08 PM
An option of the app's set up of the router, once it's online, is to copy the SSID & pwd of the old router to it.
03-03-2026 04:23 PM
That's interesting - so that is part of the set up when connecting the EE App? Trying to understand how that works though as when the new router is on line the old Bt one will have been taken out.
03-03-2026 04:38 PM
Only off the BB, not the mains.
03-03-2026 04:53 PM
How does it help by having the old router plugged in? I have found that you can enter the details manually via the app
03-03-2026 05:13 PM
So the app can access the creds over WiFi.
03-03-2026 05:44 PM
I have now managed to access the EE hub gui advanced options - by changing browser from Safari to Chrome. Have no idea what in Safari is causing the problem but it is now done.
Thanks for all the input