View Full Version : Code 401 Error
DarthM
06-23-2024, 06:22 PM
Hello on two donations I have i am getting a message stating "An error occurred: code 401". I have done a reset and also disabled provider and country lock. What would the issue be?
whats box, app, system. setup are you using?
DarthM
06-23-2024, 10:20 PM
Two different devices. One is a firestick with Tivimate app and the other is a nVidia Shield with the Tivimate app. Both are being used on different internet service providers, firestick with comcast and the Shield with Verizon Fios.
have you test on a diffrent app? try on diffrent app and if still same issue then try to generate a new code then try again.
aaronhfx
06-24-2024, 12:05 AM
Having the same issue here
running: formuler gtv with mytv online 2
same error: unable able to streeam Sever error: HTTP 401
also have reset iptv connection no luck been like this for the past 2 day for me. good thing i have backups that work fine.
DarthM
06-24-2024, 01:27 AM
Will test on different app and get back to you.
Having the same issue here
running: formuler gtv with mytv online 2
same error: unable able to streeam Sever error: HTTP 401
also have reset iptv connection no luck been like this for the past 2 day for me. good thing i have backups that work fine.
try to generate a new code, then hit reset on rocket site then try again
Will test on different app and get back to you.
sounds good. if nothing then send me all the info via pm and I will take care of reset. :)
DarthM
06-25-2024, 01:10 AM
I was able to get both of my donations working by removing a MAC address that was setup initially and doing a iptv reset.
aaronhfx
06-25-2024, 05:31 AM
try to generate a new code, then hit reset on rocket site then try again
I tried regenerating the code but it didn't seem to help. I also tried removing the MAC. On a side note, there was a software update pushed out last night june 24th for MyTVOnline 12.1.1. After the software update, it seemed to be working again. I'm not sure if it was removing the MAC or the software update that fixed it, but it's working now.
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.