@AnotherFraudUser, Welcome. Please help, recently there was a new problem with the Create Firefox Browser Instance node. The fact is that the node has stopped loading. And just waiting then turns off. Then it does not transmit a signal. It may have occurred after the KNIME update 4.6.3, but the old version also stopped working.
1 Like
Hi @Nuke_Attokurov,
thats strange.
Do you get any error message in the knime log or on the red X?
You can still open the firefox manually, right? (so not locked by another process or similiar)
Finally could you check if using another profile location changes anything?
No, Everything is right there
It does not give an error. The thing is that the node is simply loaded. And when the time comes, the waiting is interrupted. If you perform actions in an open browser window, everything is fine. The node itself does not go further along the construction.
1 Like
Okay I now at least see your issue 
Seems like the -profile argument makes the process pause…
(at least without it works for me)
Not sure why it does not work anymore but will try to figure it out
1 Like
Hi @Nuke_Attokurov,
I updated the gecko drivers to the latest version which seems to fix the problem
I started the node update process - the update will hopefully showup soon 
Could you then update the nodes and try again (you might have to add the nodes anew for this fix to apply)
Still not quite sure what changed - maybe the 4.6 selenium library was updated and required the drivers to be updated as well 
*maybe one change I already noticed with the updated drivers and -profile argument.
It seems it requires at least an empty folder to exist for the profile now
5 Likes
Thank you so much. I will follow the update.
1 Like
Hi @Nuke_Attokurov update is live (and works for me at least on my normal KNIME installation )
1 Like
Oh yeah. thanks. everything worked for me, too. it’s just awesome. thank you very much.
2 Likes
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.