Cloudron Forum

Never mind, my misunderstanding. I was able to use the wordpress-plugin "webfinger" on my main domain and just put in the my.<domain>-issuer-URL into the response, works fine!

@akammeyer Can you share how you got this working?
Same issue here - setting up tailscale to use cloudron oidc.
oidc runs under my.<domain> obviously, however I would like to use <mail>@<domain> (hosted on cloudron as mail server). It is my understanding tailscale expects the oidc to run under <domain>, additionally there needs to be a webfinger endpoint there. The last part could be solved by a LAMP stack with a simple webfinger php script, but how would tailscale accept the subdomain "my." as OIDC endpoint? Is this not an issue?

I found the problem - the photosphere plugin was activated, but it is not compatible with the current Nextcloud version. Disabling it made the images appear in folder view again.

The symlink message is directly from admin view/logging, and the symlink in the /app/data/-folder indeed exists.
Does not seem to make any problems as of now.

Hi all,

I have a new and annoying problem with my Nextcloud installation on cloudron.
There are no images when navigating to an image folder in "files" view. The message is simply "No files in here", which is evidently untrue. This has been working in January when I last checked.

Logging says there are two current errors:

• Following symlinks is not allowed ('/app/data//core' -> '/app/code/core/' not inside '/app/data/')
• Several instances of
  TypeError OCA\Files_PhotoSpheres\Sabre\PhotosphereViewerPlugin::getXmpMetadataCached(): Return value must be of type ?OCA\Files_PhotoSpheres\Model\XmpResultModel, array returned

The symlinks one is concerning, there is indeed a new symlink (todays date) that was seemingly created on the fly after the last update and my login. As far as I know (Nextcloud documentation) this is really not supported in data directories and cannot possibly work.

I have not modified the nextcloud installation manually, so I do not know what went wrong here. Something with the last update?

Grateful for any pointers, thanks!

Maik.