01-05-2022, 12:40 PM
(This post was last modified: 01-05-2022, 12:54 PM by TheOldPresbyope.)
@hjheins
I don't use Seamonkey (haven't had anything to do with integrated internet suites like it in nearly 20 years) but a quick search of their forum suggests at least one problem with many sites is that they don't recognize its useragent string. [No flame wars, please, about how site developers should or shouldn't treat useragent strings!]
If you can get to a web developers console in Seamonkey then you can examine the error messages to see if a useragent-related message appears when you browse to the moOde WebUI.
For this problem alone, you could experiment with Seamonkey config strings such as general.useragent.override to spoof using some other browser known to work. On my Linux Mint laptop, both Chrome and Firefox work well with the moOde WebUI. The current versions advertise themselves as
Chrome
Firefox
You could try overriding the Seamonkey useragent string with the equivalent from a browser of yours that works and see if the situation improves. Apparently, entering the url about:config in Seamonkey will take you to the page of currently defined strings. Search their support page for specifics about entering, say, a general.useragent.override string. (One can also override for specific sites, but that is problematic on a home network where there may be multiple players or odd DNS arrangements.)
I notice one of the Seamonkey forum posts references a database of more that 700K useragent strings detected just from Firefox browsers in the wild!!!!
Regards,
Kent
PS - an easy way to detect the useragent string of a browser is to visit the site: https://wtools.io/check-my-user-agent
I don't use Seamonkey (haven't had anything to do with integrated internet suites like it in nearly 20 years) but a quick search of their forum suggests at least one problem with many sites is that they don't recognize its useragent string. [No flame wars, please, about how site developers should or shouldn't treat useragent strings!]
If you can get to a web developers console in Seamonkey then you can examine the error messages to see if a useragent-related message appears when you browse to the moOde WebUI.
For this problem alone, you could experiment with Seamonkey config strings such as general.useragent.override to spoof using some other browser known to work. On my Linux Mint laptop, both Chrome and Firefox work well with the moOde WebUI. The current versions advertise themselves as
Chrome
Code:
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.110 Safari/537.36Firefox
Code:
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:95.0) Gecko/20100101 Firefox/95.0You could try overriding the Seamonkey useragent string with the equivalent from a browser of yours that works and see if the situation improves. Apparently, entering the url about:config in Seamonkey will take you to the page of currently defined strings. Search their support page for specifics about entering, say, a general.useragent.override string. (One can also override for specific sites, but that is problematic on a home network where there may be multiple players or odd DNS arrangements.)
I notice one of the Seamonkey forum posts references a database of more that 700K useragent strings detected just from Firefox browsers in the wild!!!!
Regards,
Kent
PS - an easy way to detect the useragent string of a browser is to visit the site: https://wtools.io/check-my-user-agent
