@PeterN1968

Woops, I thought I did . I will create a new topic.

Unfortunately you have now created a duplicate discussion in#32261 not a new issue. A new issue would be created by clicking on Issues, not Discussions.

I suggest not to try to create any new issue at this point in time. Instead follow the recommendation to manually install geckodriver and report back the results. If it is successful then we can stop there. If not, then we can do further troubleshooting steps in this discussion item.

@PeterN1968

Also, when checking what geckodriver via the terminal the following can be read in the terminal. Starting: geckodriver --version node:internal/modules/cjs/loader:1368 throw err; ^ Error: Cannot find module 'K:\PEXXXXXJK\VSSXXXX\VXXE XXXX XXXXXXXXXXXX\geckodriver' at Function._resolveFilename (node:internal/modules/cjs/loader:1365:15) at defaultResolveImpl (node:internal/modules/cjs/loader:1021:19) at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1026:22) at Function._load (node:internal/modules/cjs/loader:1175:37) at TracingChannel.traceSync (node:diagnostics_channel:322:14) at wrapModuleLoad (node:internal/modules/cjs/loader:235:24) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:171:5) at node:internal/main/run_main_module:36:49 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v22.18.0

It looks like you were using the wrong instruction to get the version ofgeckodriver. Perhaps you tried to run the incorrect commandnode geckodriver --version? According tohttps://github.com/webdriverio-community/node-geckodriver/blob/main/README.md#installing you would need to run:

npx geckodriver --version

to show the version installed.

Ah OK, I'll post it again here with attachments.

Btw, the '$env:DEBUG='cypress:server:browsers:firefox'
npx cypress open' , did not solve the issue. In the terminal I can read;

'PS K:\PERSOONLIJK\VSSTUDIO TESTSCRIPTS\VSCODE CYPRESS TESTS PETER NAUTS 23-07-2025> $env:DEBUG='cypress:server:browsers:firefox'

npx cypress open

DevTools listening on ws://127.0.0.1:59508/devtools/browser/8b66208d-8cae-47e6-a6fb-6e04dc597109
cypress:server:browsers:firefox firefox open { browser: { name: 'firefox', family: 'firefox', channel: 'stable', displayName: 'Firefox', version: '141.0.3', path: 'C:\Program Files\Mozilla Firefox\firefox.exe', majorVersion: '141', isHeaded: true, isHeadless: false }, url: 'http://localhost:59554/__/', browsers: [ { name: 'chrome', family: 'chromium', channel: 'stable', displayName: 'Chrome', version: '139.0.7258.128', path: 'C:\Program Files\Google\Chrome\Application\chrome.exe', majorVersion: '139' }, { name: 'firefox', family: 'firefox', channel: 'stable', displayName: 'Firefox', version: '141.0.3', path: 'C:\Program Files\Mozilla Firefox\firefox.exe', majorVersion: '141' }, { name: 'edge', family: 'chromium', channel: 'stable', displayName: 'Edge', version: '139.0.3405.102', path: 'C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe', majorVersion: '139' }, { name: 'electron', channel: 'stable', family: 'chromium', displayName: 'Electron', version: '130.0.6723.137', path: '', majorVersion: 130 } ], userAgent: null, proxyUrl: 'http://localhost:59554', proxyServer: 'http://localhost:59554', socketIoRoute: '/__socket', chromeWebSecurity: true, isTextTerminal: false, downloadsFolder: 'K:\PERSOONLIJK\VSSTUDIO TESTSCRIPTS\VSCODE CYPRESS TESTS PETER NAUTS 23-07-2025\cypress\downloads', experimentalModifyObstructiveThirdPartyCode: false, experimentalWebKitSupport: false, shouldLaunchNewTab: false, onBrowserClose: [Function (anonymous)], onError: [Function: onError], relaunchBrowser: [AsyncFunction (anonymous)], onBrowserOpen: [Function: onBrowserOpen] } +0ms
cypress:server:browsers:firefox available ports: { marionettePort: 59569, webDriverBiDiPort: 59570 } +9ms
cypress:server:browsers:firefox firefox directories { path: 'C:\Users\Peter\AppData\Roaming\Cypress\cy\production\browsers\firefox-stable\interactive', cacheDir: 'C:\Users\Peter\AppData\Roaming\Cypress\cy\production\browsers\firefox-stable\interactive\CypressCache', extensionDest: 'C:\Users\Peter\AppData\Roaming\Cypress\cy\production\browsers\firefox-stable\interactive\CypressExtension' } +181ms
cypress:server:browsers:firefox launching geckodriver with browser envs { MOZ_REMOTE_SETTINGS_DEVTOOLS: '1', MOZ_HEADLESS_WIDTH: '1280', MOZ_HEADLESS_HEIGHT: '720' } +6ms
cypress:server:browsers:firefox launch in firefox {
url: 'http://localhost:59554/__/',
'-new-instance',
'-start-debugger-server',
'-no-remote',
'-foreground'
]
} +0ms

It seems I also have 2 package.jsons'!!

see attachments, one is, (deleted the lines to be removed) ;

{ "devDependencies": {@./cypress-drag-drop": "github:4teamwork/cypress-drag-drop",@./cypress": "^10.0.3", "cypress": "^14.5.4" }, "dependencies": { "geckodriver": "^5.0.0" } }

and the other package.json has a lot of 'node' information, and also the mentioning of Cypress 10 !!

I do not know what happened, VSCode got updated, Cypress update , and now nothing works. I do not see any testbranch , corner left of VSCode.....

@PeterN1968

Large log files are not easy to handle if they are just pasted in to a comment as text. You could copy the log text into a file locally, use Windows' Compress to ZIP file (should be available in right-click context menu) and upload the file as an attachment to GitHub. I can compare it with running the same test on my own Windows system and see if there are differences that might point to your issue.

Ah ok, I did not know nthat was possible. Should I run that debug again and upload it as a (compacted)zip file?

@PeterN1968

Should I run that debug again and upload it as a (compacted)zip file?

That was my suggestion. If you do that, I will look at the log file, however I can't promise that I will be able to find the reason for your issue or be able to suggest a resolution.

CYPRESS VSCODE DEBUG RUN 02-09-2025.zip

@PeterN1968

When I compare logs, mine are much longer, and they do not have the following section, which looks to me like the webdriver is crashing:

    at FetchRequest._request (file:///C:/Users/Peter/AppData/Local/Cypress/Cache/15.0.0/Cypress/resources/app/packages/server/node_modules/webdriver/build/node.js:1881:19)    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)    at async startWebDriverSession (file:///C:/Users/Peter/AppData/Local/Cypress/Cache/15.0.0/Cypress/resources/app/packages/server/node_modules/webdriver/build/node.js:1177:16)    at async _WebDriver.newSession (file:///C:/Users/Peter/AppData/Local/Cypress/Cache/15.0.0/Cypress/resources/app/packages/server/node_modules/webdriver/build/node.js:1415:41)    at async Object.J (<embedded>:2521:12363)    at async Object.open (<embedded>:2521:29128)    at async v.relaunchBrowser (<embedded>:2579:45099)    at async Object.launchProject (<embedded>:2579:50964)    at async x.launchProject (<embedded>:2160:24865)    at async resolve (<embedded>:2303:47508)    at async <embedded>:829:937335  cypress:cli child event fired { event: 'exit', code: 3489660927, signal: null } +5m  cypress:cli child event fired { event: 'close', code: 3489660927, signal: null } +2ms

In the background, alongside looking at your issue, I did actually contribute to thenode-geckodriver development, and this triggered the release of a new version with many other updates in it. At the moment this can't be integrated into Cypress because thewebdriver people need to update their dependencies first. I don't really know how long that will take and they didn't respond at all last week. It could be that an update might fix your issue, but that is uncertain and the timing is also uncertain.

I can't really give you much good advice at the moment I'm afraid. If you have have the possibility to do your Firefox tests on a Linux system you might have better luck.

I'm going to have to stop here unfortunately. If I hear of any useful tips, I'll update this thread.

It's good to hear that you found a way to run Cypress with Firefox!

It sounds like you have different permissions on your system compared to mine. When I checked using a PowerShell terminal opened in regular VS Code I could run Firefox without having admin privileges. For your case, where it didn't work, if it was only a permissions issue, I would have expected to get a clearer error message instead of the apparent stack trace that you posted from your logs.

So there may still be an issue with Cypress orwebdriver etc. To follow that one up would need a simple reproducible example, and judging by the previous steps that would probably be too difficult to attempt at this time. If another user hits the same issue, that may be an opportunity to get the Cypress.io development team involved.

Since you've found a solution yourself, you can mark your own post as answer. That doesn't prevent anyone else adding their comments to this thread.

For your other questions, it doesn't sound like I can answer them for you. You could ask other users in a new thread here in Discussions or use theCypress community chat on Discord. There is no guarantee you will get an answer in either place, however there are a lot more users active in Discord.

For documentation, theChangelog andMigration Guide are good places to understand differences between releases.

If you want help about things which do not work, then you will get the best help if you describe exactly what you did, what you expected to happen and what actually happened. Also if you can provide the simplest example, that is also helpful. Try to keep one thread focussed on one topic for clarity.

You can also try to get your answers from AI, since you already have experience with this, although you need to be careful about believing everything that AI tells you!

Good luck with your Firefox testing! 🙂

Cypress Community on Discord 'banned' me, I got the response that it is a paid service now :( .
I will mark my post as answer. Thank you again, sir.

@PeterN1968

Cypress Community on Discord 'banned' me, I got the response that it is a paid service now :( .

That is not a normal experience, as the Cypress Community on Discord is intended to be a free-of-charge service, and users are joining there on a regular basis without any payment.

https://discord.com/invite/cypress should lead to the following screen:

@PeterN1968

The Discord user "Peter Nauts" was banned from the Cypress Community according to your screenshot on Aug 11, 2025. If you are banned you cannot rejoin the community.

I will ask the manager for the Discord Cypress Community next week to review the status of your Discord user. The userMEE6 is just an automation bot, it's not a person, and it doesn't reply to messages like the ones you sent asking for explanation.

OK, I am curious why I was banned. 'Unspecified' is lame.

@PeterN1968

The Cypress Community Manager has un-banned you, so if you want to try again, you should be able to re-apply.