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

Nextcloud plugin install: SSL_ERROR_RX_RECORD_TOO_LONG #26

Open
jm20122012 opened this issue Oct 14, 2020 · 1 comment
Open

Nextcloud plugin install: SSL_ERROR_RX_RECORD_TOO_LONG #26

jm20122012 opened this issue Oct 14, 2020 · 1 comment

Comments

@jm20122012
Copy link

jm20122012 commented Oct 14, 2020

FreeNAS Version: FreeNAS-11.3-U5
Nextcloud Plugin Version: 20.0.0
Nextcloud Plugin Release: 11.3-RELEASE-p10
Browser: Firefox
Network method: NAT (I know DHCP method can give untrusted domain errors which can be fixed, but I'm trying to use NAT specifically)

After installing the Nextcloud plugin and going to the initial login screen, when I attempt to login using the plugin-generated "ncadmin" account, it brings me to an error page that says:

SSL_ERROR_RX_RECORD_TOO_LONG

When I try to specify using http it auto redirects to https and ends up bringing up the same page with the SSL error.

When I try to login using Chromium it also gives an SSL error initially, but specifying http in the address bar finally brings me to the login page. When I try to log in it doesn't give me an error, but it instead just sits on the login page forever trying to login.

I read on a Github issue (from over 2 years ago) that this issue was related to some php file not being correctly copied to a certain directory, but the author didn't say where the file was supposed to be copied to. Also, apparently this bug was fixed in a subsequent version. So I'm not sure how to fix this.

I'm also not sure what log files are relevant to troubleshooting this, so please let me know where the relevant log files are located and I'll post those as well.

Any ideas on a fix for this?

@EliasGabrielsson
Copy link

The behavior you describe is expected but non less an issue.
Basically is not the server not configured with SSL.
You can close this issue and follow this thread #29.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants