Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hanging on "Connecting to the server" after launched crawling #24

Open
Entretoize opened this issue Nov 12, 2024 · 7 comments
Open

Hanging on "Connecting to the server" after launched crawling #24

Entretoize opened this issue Nov 12, 2024 · 7 comments
Labels
bug Something isn't working

Comments

@Entretoize
Copy link

It used to work but now when I click on "Crawl now" it just write "Connecting to the server, please wait..." and never change, the crawling never happen.

@Entretoize Entretoize added the bug Something isn't working label Nov 12, 2024
@StJudeWasHere
Copy link
Owner

Can you provide more details? URL, crawler options or any error printed out.

@StJudeWasHere StJudeWasHere removed their assignment Nov 12, 2024
@renatop7
Copy link

@StJudeWasHere I'm having the same problem while running the docker image.

Trying to crawl this URL with default options:
https://www.centralsuldeleiloes.com.br

When opening the console on Chrome I can see this error:
WebSocket connection to 'ws://localhost:3001/crawl/ws?pid=1' failed:

@Entretoize
Copy link
Author

Entretoize commented Nov 13, 2024

For me, I have that error in the console:

Mixed Content: The page at 'https://seonaut.mydomain.fr/crawl/live?pid=4' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://seonaut.mydomain.fr/crawl/ws?pid=4'. This request has been blocked; this endpoint must be available over WSS.

And I'm not sure, but maybe the crawling is done, but it give no update about that...

@StJudeWasHere
Copy link
Owner

Mixed Content: The page at 'https://seonaut.mydomain.fr/crawl/live?pid=4' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://seonaut.mydomain.fr/crawl/ws?pid=4'. This request has been blocked; this endpoint must be available over WSS.

If you're using https, make sure to update the server url in the config file as well. Otherwise it could cause this kind of error.

@Entretoize
Copy link
Author

You mean the "config" file ? Should I redo docker-compose up -d --build after that ? Will it erase everything ?

@StJudeWasHere
Copy link
Owner

Yes, you only need to build the app service docker-compose up -d --build app.

@Entretoize
Copy link
Author

Entretoize commented Nov 13, 2024

Ok, I did that and now I get:

WebSocket connection to 'wss://seonaut.mydomain.fr/crawl/ws?pid=2' failed

I tried that for my apache configuration:

<VirtualHost *:443>
  ServerName seonaut.mydomain.fr

  ProxyPass / http://localhost:9000/  ##tried with https but got error 500
  ProxyPassReverse / http://localhost:9000/

Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /etc/letsencrypt/live/mydomain.fr/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/mydomain.fr/privkey.pem

ProxyPassMatch ^/crawl/ws/(.*)$ wss://localhost:9000/crawl/ws/$1
ProxyPassReverse /crawl/ws/ wss://localhost:9000/crawl/ws/

</VirtualHost>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants