App-Breaking Login-Issue on ARM-Version about nextcloud-snap HOT 10 CLOSED

it seems as though you have skipped some configuration steps...

your logs are showing the following recurring errors:

Jan 15 22:00:54 rpi5 nextcloud.apache[10965]: No certificates are active: using HTTP only
Jan 15 22:00:57 rpi5 nextcloud.apache[11162]: error: cannot communicate with server: Post "http://localhost/v2/snapctl": read unix @->/run/snapd-snap.socket: read: connection reset by peer
....
Jan 15 22:00:57 rpi5 nextcloud.apache[11672]: AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
Jan 15 22:00:57 rpi5 systemd[1]: snap.nextcloud.apache.service: Deactivated successfully.

log error messages:

No certificates are active: using HTTP only

• enable HTTPS encryption? See Configuration first section enable HTTPS encryption with Lets Encrypt

  • that should resolve the logging in issue

Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message

• you may want to check out hosts & FQDN configuration to resolve the second recurring log message. See here for your setup

  • this is optional but recommended

hey there

I use a reverse-proxy.
the issue also occurs when setting it up direclty wiht the builtin letsencrypt without the reverse-proxy.

from nextcloud-snap.

@scubamuc
I just did all of these changes to check if they would fix the issue. they don't.

I have five installations on x86 with the same setup. there the problem does not occur.
on most installs I use SSO to login normal users but I have a builtin admin which can login without any issue.
besides the user-synch & SSO there is no difference in the setup. + there is one install where I literally used the same setup as on RPIs and it didn't occur.
I'm replacing this setup with the RPI5 right now.

I have an automated script which I use for all installations so the configuration cannot be the issue,
the issue only happens on my three RPI setups (2* RPI4, 1* RPI5)

from nextcloud-snap.

Actually your links helped in the end I just failed with the setting of:
overwriteprotocol

BUT.. it is also not set in my x86 setups, and there it works.
readign the docs it seems as if it's not always needed.

so thank you a lot and it actually fixes it.

from nextcloud-snap.

outputofscript.txt

from nextcloud-snap.

it seems as though you have skipped some configuration steps...

your logs are showing the following recurring errors:

Jan 15 22:00:54 rpi5 nextcloud.apache[10965]: No certificates are active: using HTTP only
Jan 15 22:00:57 rpi5 nextcloud.apache[11162]: error: cannot communicate with server: Post "http://localhost/v2/snapctl": read unix @->/run/snapd-snap.socket: read: connection reset by peer
....
Jan 15 22:00:57 rpi5 nextcloud.apache[11672]: AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
Jan 15 22:00:57 rpi5 systemd[1]: snap.nextcloud.apache.service: Deactivated successfully.

log error messages:

No certificates are active: using HTTP only

• enable HTTPS encryption? See Configuration first section enable HTTPS encryption with Lets Encrypt
  • that should resolve the logging in issue

Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message

• you may want to check out hosts & FQDN configuration to resolve the second recurring log message. See here for your setup
  • this is optional but recommended

from nextcloud-snap.

thanks for that info...

double check proxy manager handles encryption
see last section

and

FQDN for Nextcloud snap instance, vm or container behind reverse proxy with termination

so this is not a Nextcloud snap issue...

from nextcloud-snap.

@ne0YT, so you're assuming it'll have something to do with ARM... we'll have to see if the devs have any input.

Sorry for being overzealous 🤐

from nextcloud-snap.

@ne0YT, on a personal note, I'm interested to see your script. is there any chance you could upload it to your github so that I could have a look see?

I've put mine here so you might want to compare.

from nextcloud-snap.

I'm really sorry.. I rechecked everything.. 😬
my reverse-proxy for the x86 setup is configured to use ssl for the backend too..
so just a fault on my side. exactly how you pointed out.
thank you so much agan for the help

from nextcloud-snap.

no problem, glad I cloud help

from nextcloud-snap.