EH plugin can not connect to ex gallery

[gth7754125]

LRR Version and OS
Windows docker container: latest
win10

Bug Details
Error: SSL connect attempt failed at /home/koyomi/lanraragi/script/../lib/LANraragi/Plugin/Metadata/EHentai.pm line 191.

When i search for metadata tags manually, it runs failed.

docker compose file

version: '3'

services:
  lanraragi:
    image: difegue/lanraragi
    container_name: lanraragi
    ports:
      - 3000:3000
    volumes:
      - .\content:/home/koyomi/lanraragi/content
      - .\database:/home/koyomi/lanraragi/database
    restart: always

[Difegue]

I believe something in your Windows+Docker setup is preventing the container from accessing the internet.

Maybe this discussion from the Docker for Windows repo can help? docker/for-win#2760

[xyzeratul]

I have the same issues:
unraid 6.82 + docker 19.03.5

Error: Connect timeout at /home/koyomi/lanraragi/script/../lib/LANraragi/Plugin/Metadata/EHentai.pm line 191.

batch tagging never work, however I can update meta data one by one, which is really slow and painful

[Difegue]

If individual plugin execution works but not batch tagging, you might have websockets blocked for some reason ?
There might be more info in your browser console.

Moving this to a discussion as it's seemingly not an issue with the software.

[fullmetal1]

I have a similar issue.

Manjaro with a portable install of 0.8.7

I've tried the latest IO::Socket::SSL (2.075), the one listed in cpanfile, and the one requested by the error message.

How would I check if my websockets are blocked? This server doesn't run in nginx

[Difegue]

I don't believe this is caused by the websockets at this point - You can try running plugins from the "Edit" window of any archive to make sure of that.

As for that error, uhhh I've never seen it, might be interesting to google for it and see if you're missing a package on the manjaro side or something?

[fullmetal1]

Found a solution here

Somewhere in setup_cors() in lib/LANraragi/Login.pm you need to add

$self->res->headers->header('Access-Control-Allow-Methods' => 'GET, OPTIONS, POST, DELETE, PUT');

I am not at all familiar with Mojo or webserver development so I don't know the consequences, security or otherwise, of doing this beyond it fixing the issue that I saw.

[Difegue]

I have no idea why this would trigger a SSL error, but allowing all common methods instead of just GET when CORS is enabled seems like a good idea. Will patch that in and we'll see how it goes 👍 Thanks for the report!