I still have the same problem (1 year later) : PROXY ADDRESS=zproxy.lum-superproxy.io:22225 Gives this error: "BadParameter: expected server name or IP address with port number as parameter 1, line: x" Its the hypen that causes it. I could replace ...

I still have the same problem (1 year later) : PROXY ADDRESS=zproxy.lum-superproxy.io:22225 Gives this error: "BadParameter: expected server name or IP address with port number as parameter 1, line: x" Its the hypen that causes it. I could replace ...

... characters Can you help me ? Hum, Thread approved even if I'm not "really sure" you are a "real" User because of your "dirty" IP through 'M247' Proxy/Cloud Service only used by "fake" Users and Spammers on our Forum, I usually disapprove nearly automatically Posts/Threads from some 'M247' IP..., ...

... TLS 1.2 of course...) It could be that the Site is performing some IP-Check and only "expects" Users to connect from a local ("real" = non-VPN/non-Proxy) 'CA' IP (while I have an 'NL' IP), but I have the "Feeling" the Site doesn't even come that far, and is simply not responding at all... :o

... related to iMB v12.x usually don't come to the Forum as Users of a Licensed Version have Direct Access to TechSup, and don't use an Anonymizer Proxy, ah-ah...! But OK, fair enough, the Forum is Users helping Users... :wink: Alright, about your Issue, I would first say that I personally consider ...

... my Sig...) - Always a "good Idea" to read the Forum Rules when you join a Tech Forum... :idea: - Never a "good Idea" to hide behind 'Hide My Ass' Proxy when you register to a Tech Forum, or you automatically get the "Reputation" of that IP which is also used by Spammers..., and will automatically ...

... it's IE11. I think my issue is more of general tech than scripts. All my scripts work ok under normal circumstances. However I've configured my proxy not to trust any cert (WTF, yes I know, but it's for testing purposes.) Chrome works (no cert error popups) with the parameter enabled, but IE ...

... listed (May 2020) as "Unsupported" on FF, are actually very well supported in v8.9.7 for FF: 'EVENT' + 'FILEDELETE' + 'FILTER' + 'ONDIALOG' + 'PROXY' + '!SINGLESTEP'... ... And there might be a few others, I only had a quick Look... ('FILTER' is a bit broken btw, since FF52...) Thank you, thank ...

... listed (May 2020) as "Unsupported" on FF, are actually very well supported in v8.9.7 for FF: 'EVENT' + 'FILEDELETE' + 'FILTER' + 'ONDIALOG' + 'PROXY' + '!SINGLESTEP'... ... And there might be a few others, I only had a quick Look... ('FILTER' is a bit broken btw, since FF52...)

... it's IE11. I think my issue is more of general tech than scripts. All my scripts work ok under normal circumstances. However I've configured my proxy not to trust any cert (WTF, yes I know, but it's for testing purposes.) Chrome works (no cert error popups) with the parameter enabled, but IE ...

... it's IE11. I think my issue is more of general tech than scripts. All my scripts work ok under normal circumstances. However I've configured my proxy not to trust any cert (WTF, yes I know, but it's for testing purposes.) Chrome works (no cert error popups) with the parameter enabled, but IE ...

... actually, with some excellent Work from the same Advanced User @thecoder2012 (applied to v8.9.7 for FF): 8) - Hyphen (-) Not Recognized in PROXY ADDRESS

Hi, Thanks for your answer. I'm on windows 10, Entreprise Licence, last iMacros version. I need to use firefox profiles in order to using proxy settings (I'm actually using iMacros browser with "PROXY" function but I want to switch to firefox). I have a lot of profiles (about 1000) in several ...

(I also edited my previous Post, ah-ah...! :wink: ) And yep indeed, "about:support" was another example, and I think in v10.0.2 for FF, you also have a Pb with "about:blank"... (You have some Thread on the Forum about it... ... Hum, which leads to another very nasty (and Blocking in my Opinion) Bug ...

You possibly also have the same or a similar Bug in the 'URL GOTO' Command, have you seen that "Reference"...? I already reported and "analyzed" it 3 years ago, but it was never "acknowledged" by @TechSup... :wink: There's no problem with hyphens in the URL. For example, the following works just fi...