yang991178 / fluent-reader

Modern desktop RSS reader built with Electron, React, and Fluent UI
https://hyliu.me/fluent-reader/
BSD 3-Clause "New" or "Revised" License
7.8k stars 425 forks source link

Help need for setting localhost Nextcloud News #531

Open GaryRandom opened 1 year ago

GaryRandom commented 1 year ago

I have run a Nextcloud docker in my NAS and want to sync RSS feeds among my devices in the local network. I chosen a Nextcould service in Fluent Reader and fill the blank as following:

endpoint: https://localhost:443/index.php/apps/news/api/v2 or https://localhost:443/index.php/apps/news/api/v2/sync
username: my Nextcloud user name
password: my Nextcloud password

and then Fluent Reader always report Please check the service configuration or network status.

Any help for this?

ProfessorCode212 commented 1 year ago

I have the same issue over here as well.

image

There seems to be a similar issue for Inoreader as well. #438 (Also check #525)

ProfessorCode212 commented 1 year ago

@GaryRandom Did you create a self-signed SSL certificate for your local NextCloud instance?

At least on my end, that appears to be the issue.

[xxxx:ERROR:cert_verify_proc_builtin.cc(670)] CertVerifyProcBuiltin for IP_ADDRESS failed:
----- Certificate i=0 (CN=localhost) -----
ERROR: No matching issuer found

[xxxx:ERROR:ssl_client_socket_impl.cc(983)] handshake failed; returned -1, SSL error code 1, net_error -202

@yawks @yang991178 Could you please provide an option to ignore certificate errors?

yang991178 commented 1 year ago

See #409. If you're just accessing through localhost, then I think using HTTP instead of HTTPS is totally fine?

ProfessorCode212 commented 1 year ago

@yang991178 I took your suggestion and disabled "force HTTPS" for NextCloud. Unfortunately, I still get an error saying Cannot connect to service as before. I am not getting any errors in the terminal either.

I also tried accessing my NextCloud instance via HTTP on the browser and I get an error saying it was a "bad request" there as well. NextCloud appears to be a bit picky about using HTTPS. I'd appreciate it if you could reconsider this. :slightly_smiling_face:

ProfessorCode212 commented 1 year ago

Also, regarding your concern on providing an option to ignore certificate errors, couldn't it be hidden under something like Advanced options? That should give enough of a warning and still allow anyone who needs it to use the option.

yang991178 commented 1 year ago

I can look into an option to ignore certificate errors for localhost when I have the time

ProfessorCode212 commented 1 year ago

Thanks. Although, most people would run NextCloud on a separate machine from the one they would normally use. Instead, what about allowing to ignore certificate errors for common IP address ranges (10.0.0.0 – 10.255.255.255, 192.168.0.0 – 192.168.255.255) used for local networks?