Closed soosrol closed 2 years ago
TheDan64
commented
5 years ago I've also run into this issue, pretty much identically to what @bamBrewing described but in Windows and FF 66. FF will open with the specified profile but then geckdriver will not do anything with it eventually crashing with a 500 ISE...
edmolten
commented
5 years ago I needed to use the profile and also some unsigned extensions, so I used a developer edition of Firefox 66. Even using the workaround, Firefox still created a "dev profile" and was copying the content of my profile to it, but my profile was used anyway, super weird. As my profile is quite big, I didn't want it to be copied every time I used it, so I found that adding an empty file called ignore-dev-edition-profile alongside the profiles.ini file made Firefox stop copying it.
Ah i understand now... In case anyone else was struggling in the same way as I was the
--marionette-portcommand line option is applied when starting geckodriver not starting firefox.So workaround steps are:
- rename /usr/bin/geckodriver to /usr/bin/geckodriver2
- use @soosrol 's script to point to the renamed executable file and save this script in the original /usr/bin/geckodriver location
Many thanks for the workaround, guys! All back up and running now :-)
umarch06
commented
5 years ago @artemklushin I tried your solution and it works, but the problem is that if you will try to run firefox with next profile - it will open the last used profile and that's totally weird. are you experiencing the same issue?
lacell75
commented
5 years ago I need this correction asap. I didn't find workaround for my case: I use 4 instances of firefox with selenium Grid. I can't use a fix marionette port.
lacell75
commented
5 years ago Hello, @hornschorsch , your geckodriver patched is for linux or windows version?
veliakiner
commented
4 years ago @soosrul's excellent workaround inspired me to discover you can do the same thing using the service args argument for webdriver.Firefox:
service_args=["--marionette-port", "2828"]
kretschmannj
commented
4 years ago I got the -profile option to work as expected by adding --marionette-port . Here's the firefox section from my nightwatch.conf.js file ...
firefox: { desiredCapabilities: { browserName: 'firefox', alwaysMatch: {'moz:firefoxOptions': {args: ['-profile', 'Firefox_Profile/Nightwatch']}} }, webdriver: { start_process: true, server_path: (Services.geckodriver ? Services.geckodriver.path : ''), 'cli_args': ['--marionette-port', '2828'] } } Note that I'm using a relative path to the profile file which I have saved in the Firefox_Profile folder in my project. Also, the marionette-port number doesn't seem to matter much so I just picked some arbitrary value.
Note that this is for Nightwatch "webdriver" not selenium. I have not figured out how to use a custom profile with Nightwatch selenium.
tttony
commented
4 years ago @umarch06 For c# you can try next solution:
FirefoxDriverService ffDriverService = FirefoxDriverService.CreateDefaultService(<driver path>); ffDriverService.BrowserCommunicationPort = 2828; IWebDriver driver = new FirefoxDriver(ffDriverService, <instance of FirefoxOptions>);It's works for me with profile in custom directory.
This worked right away!! After long fighting to fix this problem... Thanks
I created a new profile running firefox.exe -p then I and setted in the options the profile path to run with -profile argument:
FirefoxOptions options = new FirefoxOptions();
options.AddArguments("-profile", @"C:\Users\<user>\AppData\Roaming\Mozilla\Firefox\Profiles\8oh5nwar.selenium"); There was no need to parse the marionette port in the prefs.js file, I think it's because the profle is from actual firefox profile(?) in that file there is no marionette-port option
sybrandy
commented
4 years ago Hello,
I'm having the same issue trying to use a custom profile using the selenium-side-runner CLI tool. My current .side.yml looks liek this:
capabilities:
acceptInsecureCerts: true
browserName: firefox
moz:firefoxOptions:
args: ["-profile", "/tmp/profile/"]
log:
level: traceBelow is some sample output from my test run:
16:42:53.116 INFO [ActiveSessionFactory.apply] - Capabilities are: {
"acceptInsecureCerts": true,
"browserName": "firefox",
"moz:firefoxOptions": {
"args": [
"-profile",
"\u002ftmp\u002fprofile\u002f"
],
"log": {
"level": "trace"
}
}
}
16:42:53.116 INFO [ActiveSessionFactory.lambda$apply$11] - Matched factory org.openqa.selenium.grid.session.remote.ServicedSession$Factory (provider: org.openqa.selenium.firefox.GeckoDriverService)
1594744973172 mozrunner::runner INFO Running command: "/usr/bin/firefox" "-marionette" "-profile" "/tmp/profile/" "-foreground" "-no-remote"
1594744973174 geckodriver::marionette DEBUG Waiting 60s to connect to browser on 127.0.0.1:34696
1594745033269 mozrunner::runner DEBUG Killing process 411
1594745033276 webdriver::server DEBUG <- 500 Internal Server Error {"value":{"error":"timeout","message":"connection refused","stacktrace":""}}Does anyone have an idea as to how I can work around this using the runner? I'm using version 3.141.59 of the selenium standalone Firefox webdriver image.
baptx
commented
4 years ago Hello, I tried to use a custom profile like that but it did not work, did I do something wrong?
Go to a Firefox profile folder and create a ZIP file with the profile files using this command: zip -r profile.zip *
Create the Base64 file with this command: base64 profile.zip > profile_zip_base64.txt
Use the profile in the Selenium WebDriver script using Node.js like this (replace /tmp with the correct folder name where you copied the file):
var webdriver = require("selenium-webdriver");
var firefox = require("selenium-webdriver/firefox");
var options = new firefox.Options();
options.addArguments("-profile /tmp/profile_zip_base64.txt");
var capabilities = webdriver.Capabilities.firefox();
var driver = new webdriver.Builder()
.usingServer("http://localhost:4444")
.withCapabilities(capabilities)
.setFirefoxOptions(options)
.build();
driver.get('https://www.google.com/?hl=en');Then I start GeckoDriver with the command: geckodriver --marionette-port 2828
But when I execute the script, it opens the web page in my default Firefox profile. The ZIP profile that I created should also contain a cookie named "test" that I created on google.com but I don't see it in the web console.
I also read that @whimboo said that it is possible to use the --profile argument of Firefox (https://github.com/mozilla/geckodriver/issues/1773#issuecomment-691023261). What do you mean by "But keep in mind that the latter isn't that easy due to some missing features."? Do you have a working example?
dncpax
commented
3 years ago Ah i understand now... In case anyone else was struggling in the same way as I was the
--marionette-portcommand line option is applied when starting geckodriver not starting firefox.So workaround steps are:
- rename /usr/bin/geckodriver to /usr/bin/geckodriver2
- use @soosrol 's script to point to the renamed executable file and save this script in the original /usr/bin/geckodriver location
Many thanks for the workaround, guys! All back up and running now :-)
I know it's been a while, but I'm struggling with this bug... and for the life of me I cannot figure out what the workaround is!!? What's this script? Can anyone still help?
baptx
commented
3 years ago @dncpax in case it helps, the workaround I used is to create a custom WebExtension and load it with Selenium WebDriver instead of loading a whole Firefox profile, for example to have cookies before doing an HTTP request: https://github.com/SeleniumHQ/selenium/issues/8693#issuecomment-691498083 The advantage is that it will be more lightweight, you only load what you need. But profile support could be useful also. Without profile support, if you need to save cookies / localStorage / sessionStorage, you would need to to it manually (writing and reading data in a file).
Edit: I also don't know what is @soosrol 's script mentioned by @stewart-r at https://github.com/mozilla/geckodriver/issues/1058#issuecomment-350254437, more information are welcome.
dncpax
commented
3 years ago @baptx thanks for replying. My goal is to login automatically so Im using a profile for that which has autoauth extension installed and configured. With this bug I'm stuck. I also use selenium-side-runner to avoid scripting tests. So I'm really stuck... This is such an old bug...
baptx
commented
3 years ago @dncpax the workaround I use should work for you also, if you load the WebExtension instead of the profile (and write / read session ID stored in e.g. cookies to a file if you want to stay logged in next time you execute the script).
dncpax
commented
3 years ago @baptx that would be wonderful... but I'm working with windows auth... that's the only reason I need a profile and the autoauth extension. Would this work with a webextension?
hornschorsch
commented
3 years ago A fix for this problem is above in this thread. No idea why it isn't implemented.
dncpax
commented
3 years ago @hornschorsch same here... I know everyone does what he/she can, but someone posted 10lines of working code, and somehow it wasn't picked up... not to rant or anything...
baptx
commented
3 years ago @dncpax What do you mean by windows auth? It is probably possible to do it without profile if you write and read profile data to a file. Where is the 10 lines of working code exactly?
dncpax
commented
3 years ago windows integrated authentication...
globalcitizen
commented
3 years ago This bug has been open for 4 years.
Still seeing this issue on geckodriver-0.30.0 with selenium-webdriver-4.0.3 .
-P <profilename>-p </path/to/profile>-p </path/to/profile> instead of -P <profile_name>
saifahn
commented
2 years ago @globalcitizen Does using -p over -P actually use the profile correctly? Thanks :)
globalcitizen
commented
2 years ago @saifahn Sorry test environment long since destroyed.
ToxicFrog
commented
2 years ago @globalcitizen Does using
-pover-Pactually use the profile correctly? Thanks :)
I've experimented with this and it does not appear to -- -p and -P are aliases for each other, --profile has no short equivalent. So when running with -p path/to/profile/dir, it looks for a profile with that name, doesn't find one, and ends up running in an ephemeral profile instead -- you can verify this by running it in non-headless mode and looking at about:profiles.
If you use -P profile-name, -p profile-name, or --profile path/to/profile, it loads the profile fine, but port autonegotiation doesn't work, as discussed above.
whimboo
commented
2 years ago Can someone who still sees this problem please provide the code that you are using with Selenium? When using a custom profile you will have to make sure to instruct geckodriver to use the appropriate port for Marionette which should be passed to FirefoxDriver() (at least for the Python binding) as service_args.
ToxicFrog
commented
2 years ago @whimboo here's how I'm using it, via etaoin:
(wd/firefox
{:args ["-P" "test.profile"]
:args-driver ["--log" "trace" "--marionette-port" port]
:log-stdout "/dev/tty"
:log-stderr "/dev/tty"
:size [1920 2160]
:path-browser firefox-bin
:locator "css selector"})Note that by "doesn't work" earlier, I don't mean "it doesn't load the profile", I mean "it loads the profile but doesn't autonegotiate a port to use for Marionette, so unless you manually set one in prefs.js or user.js ahead of time, it'll always pick 2828 and you can only have one instance running at a time".
In the above code, I've constructed an appropriate user.js by hand and port is passed in via the command line, but this doesn't scale; absent a fix for this, I'm probably going to have to write something that figures out where the profile directory is, selects a port, and writes an appropriate user.js before launching geckodriver with --marionette-port (hoping that nothing else has stolen that port in the intervening time).
whimboo
commented
2 years ago @ToxicFrog thank you for the details. For now I don't have a proper solution yet, but I can say that we are working on it. But please bear with us that it might take some time to finish it. For now here a workaround:
marionette.port set to 0.--marionette --profile %profile_path% and other arguments if needed%profile_path%/MarionetteActivePort for the port Marionette is using (available since Firefox 95)--connect-existing --marionette-port %port% to connect geckodriver to MarionetteWe are aware that this is not optimal but at least a start so that scaling won't be a problem for you anymore. With the above steps each instance of Firefox and Marionette will pick up a free and unique system port.
Ongoing work can be tracked via: https://bugzilla.mozilla.org/show_bug.cgi?id=1240830#c16 and ff. For now only step 1 has been done.
whimboo
commented
2 years ago Good news. Recently we landed a patch for geckodriver which by default would allow Marionette to use a system allocated port, and geckodriver then reads that port from the Firefox profile. Anyone with the problem on this issue could you please check this Nightly build of geckodriver. Just click the green gd-s job for your platform, and download the geckodriver.tar.gz or geckodriver.zip from by clicking the link in the lower pane.
When testing please don't force a Marionette port via the --marionette-port argument of geckodriver because that would turn off the new code path. Also you have to make sure to at least use a Firefox 95 release.
Please let us know if it works or not. If it's the latter please attach a trace log. Thanks!
ToxicFrog
commented
2 years ago I've been otherwise occupied this week but I'll try that out next time I'm tinkering with this, which should hopefully be soon. Thanks!
ToxicFrog
commented
2 years ago No luck.
In short: geckodriver starts up, and starts firefox; firefox does not write the MarionetteActivePort file, and geckodriver spins endlessly waiting for it to appear until its parent process watchdogs and kills it.
The runtime profile directory it's looking for in /run/user does exist.
The profile has a blank user.js in the firefox config directory, and the user.js in /run/user has marionette.port set to 0.
It looks like geckodriver is doing the right thing but FF isn't writing the MarionetteActivePort file; any advice on next steps?
1644624687959 geckodriver INFO Listening on 127.0.0.1:45335
1644624688072 webdriver::server DEBUG -> POST /session {"desiredCapabilities":{"loggingPrefs":{"browser":"ALL"},"moz:firefoxOptions":{"binary":"/nix/store/pjxk10j2cbj9ld1xz78wq1m1jggylcy2-firefox-96.0.3/bin/firefox","args":["-width","1920","-height","2160","--new-window","https://[redacted]/","--headless","-P","ca.ancilla.hangbrain"]}}}
1644624688072 webdriver::command WARN You are using deprecated legacy session negotiation patterns (desiredCapabilities/requiredCapabilities), see https://developer.mozilla.org/en-US/docs/Web/WebDriver/Capabilities#Legacy
1644624688072 geckodriver::capabilities DEBUG Trying to read firefox version from ini files
1644624688072 geckodriver::capabilities DEBUG Trying to read firefox version from binary
1644624688144 geckodriver::capabilities DEBUG Found version 96.0.3
1644624688145 mozrunner::runner INFO Running command: "/nix/store/pjxk10j2cbj9ld1xz78wq1m1jggylcy2-firefox-96.0.3/bin/firefox" "--marionette" "-width" "1920" "-height" "2160" "--new-window" "https://chat.google.com/" "--headless" "-P" "ca.ancilla.hangbrain" "-no-remote"
1644624688145 geckodriver::marionette DEBUG Waiting 60s to connect to browser on 127.0.0.1
1644624688145 geckodriver::browser TRACE Failed to open /run/user/8509/rust_mozprofileKu4Rax/MarionetteActivePort
1644624688145 geckodriver::marionette TRACE Retrying in 100ms
*** You are running in headless mode.
1644624688246 geckodriver::browser TRACE Failed to open /run/user/8509/rust_mozprofileKu4Rax/MarionetteActivePort
1644624688246 geckodriver::marionette TRACE Retrying in 100ms
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: Unable to open a connection to the X server (t=0.12545) [GFX1-]: glxtest: Unable to open a connection to the X server
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: Unable to open a connection to the X server (t=0.12545) |[1][GFX1-]: glxtest: libEGL initialize failed (t=0.125485) [GFX1-]: gl
xtest: libEGL initialize failed
1644624688346 geckodriver::browser TRACE Failed to open /run/user/8509/rust_mozprofileKu4Rax/MarionetteActivePort
1644624688346 geckodriver::marionette TRACE Retrying in 100ms
[...many more such messages redacted...]
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: Unable to open a connection to the X server (t=0.12545) |[1][GFX1-]: glxtest: libEGL initialize failed (t=0.125485) |[2][GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt (t=0.790276) [GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dtThe X11/GL errors show that FF is starting up successfully, and are normal -- it's running headless on a machine with no X server. I can see that Geckodriver and Firefox are both running:
$ pgrep -laf gecko
1504017 geckodriver --port 35947
$ pgrep -laf firefox
1517150 /nix/store/pjxk10j2cbj9ld1xz78wq1m1jggylcy2-firefox-96.0.3/bin/.firefox-wrapped --marionette -width 1920 -height 2160 --new-window https://[redacted]/ --headless -P ca.ancilla.hangbrain -no-remote
$ firefox --version
Mozilla Firefox 96.0.3
$ geckodriver --version
geckodriver 0.30.0 (b9121c1a4330 2022-01-27 23:34 +0200)Interesting case. So you are specifying a profile name from the profile manager when using "-P","ca.ancilla.hangbrain". But geckodriver doesn't know about the profile location and as such is checking the wrong directory. Can you please check by using the profile path via "-profile", "%path_to_profile%"?
For the -P issue I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1755261.
ToxicFrog
commented
2 years ago I can do that as a one-off, but not in the general case since the mapping from profile name to profile directory isn't straightforward
If I use -CreateProfile "foo path/to/foo", can I then subsequently use -profile path/to/foo? In that case all the profile names are predictable and I can use this.
In any case, I'll give it a shot and report back.
whimboo
commented
2 years ago @ToxicFrog can you explain why you need -CreateProfile? You can start Firefox with -profile path to let it populate the folder with a fresh profile. That way it doesn't pollute the profile manager entries. Note that by using the profile manager the path to the profile is platform dependent.
ToxicFrog
commented
2 years ago I'd completely forgotten about that -- I think that would work better for my use case anyways. I'll try that out and report back, thanks.
ToxicFrog
commented
2 years ago It works! It even works with an existing profile, as long as you don't have marionette.port set in it.
whimboo
commented
2 years ago It works! It even works with an existing profile, as long as you don't have
marionette.portset in it.
This is great to hear! So yes, marionette.port should not be set or have a value of 0. Thanks for the verification.
If there is still a problem related to this feature please file a new issue. Otherwise we will ship this new feature with the next geckodriver 0.31.0 release.
whimboo
commented
2 years ago For the
-Pissue I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1755261.
FYI this bug is now fixed and we marked the usage of -P as deprecated. Instead of the profile name the profile path has to be used.
MagdelineNg
commented
6 months ago @whimboo Hi, I am referencing this issue to automate the existing Firefox instance by connecting to the marionette.port. According to this issue and many others, it seems like the default port is 2828 for marionette, but I realised the selenium driver connects to the port shown in the image instead (and that marionette.port variable changes every time I relaunch the Firefox browser). Is there a way to fix the marionette port when launching Firefox?
Current workflow:
Launching Firefox
'C:\Program Files\Mozilla Firefox\firefox.exe' - marionette
'C:\Program Files\Mozilla Firefox\firefox.exe' - marionette -start-debugger-server=2828 #also tried this but marionette.port still does not reflect 2828Launching Selenium GeckoDriver
driver = webdriver.Firefox(executable_path=GeckoDriverManager().install(), service-args=['--marionette-port', '65493', '--connect-existing']) #i don't want to hardcode the port, is there a way to get the Firefox marionette.port variable?
print(driver.page_source)First note that -start-debugger-server is not an option that controls Marionette. Instead it is related to DevTools. So you can omit that argument.
Regarding connecting to an existing instance of Firefox this is not yet fully supported. Especially not with random ports given that geckodriver cannot read the MarionetteActivePort file from the user's Firefox profile. But if you know which profile is used you could read the port yourself and feed it as argument to the Selenium driver.
System
Testcase
Expected result
Actual result
Notes
fo.addArguments("-profile", "./firefoxprofile");firefox.exe -profile "path/to/profile"also works.Stacktrace
Trace-level log