Your web server is not properly set up to resolve "/.well-known/webfinger". "/.well-known/nodeinfo". about nextcloud-snap HOT 26 CLOSED

Gonna test in a few hours and report

from nextcloud-snap.

no, there are not reverse proxies, but as I say, reconfiguration to without sub-folder resolves my 'webfinger' issue
You are right, complaints about Data directory must be discussed in another thread
/over

from nextcloud-snap.

I'm not using the social app.

But I get those errors in the status check.

Not that I really care but would be good to know why.

I did not have this problem on truenas nextcloud (I recently migrated to snap)

from nextcloud-snap.

@Pilzinsel64, do you have thoughts about these warnings?

As long as the social app is not enabled or even installed, this warning should't appear. If this appear in on a clean install without any additional apps, it might be the issue @sbe-arg already linked: nextcloud/server#45505 (comment) Let's see what comes out of your tests. :)

from nextcloud-snap.

Ill try to do further testing this week. I was out of action for a day and a bit.

from nextcloud-snap.

@sbe-arg now I've seen some mention that setting overwriite-cli might resolve this issue... its worth a try right?

Set overwrite-cli

  sudo nextcloud.occ config:system:set overwrite.cli.url --value="https://cloud.my.domain.xyz"

from nextcloud-snap.

I already have
'overwrite.cli.url' => 'https://nextcloud.example.com',

but I get somewhat drastic solution, I reconfigure system now without sub folder, just use sub domain and wildcard LE certs

now only complaints is about Data directory accessible to internet, what is not true at all:
nextcloud/server#45087 (comment)

from nextcloud-snap.

Not sure if resolves it then if it hides it behind something else.

from nextcloud-snap.

hey mate,
this is certainly an upstream issue and not a snap issue... check https://help.nextcloud.com for similar issues. as well as #45033 and #46255 for upstream PR.

if you're not happy with that, then I'll gladly reopen the issue 🤭

from nextcloud-snap.

probably related to this nextcloud/documentation#6157 (comment)

from nextcloud-snap.

@sbe-arg welcome back

yeah, then you'll need those entries in NPM advanced settings from NC29... but may also work for NC28 if you're getting those errors.

from nextcloud-snap.

@sbe-arg

I get those errors in the status check...

can you post a screenshot?

would be good to know why.

please give me a shout if you find out 👍

from nextcloud-snap.

@Pilzinsel64, do you have thoughts about these warnings?

@sbe-arg compare your apps list with recommended default apps

from nextcloud-snap.

Ill share the app list but the only 3 apps I installed aside the default set are:

Talk
Office
Collabora server

• installed snap
• configured reverse proxy settings
• installed the 3 apps
• restored files

That was my migration nothing fancy mainly moving files from one setup to another.

from nextcloud-snap.

nextcloud/server#45505 (comment)

from nextcloud-snap.

@sbe-arg

nextcloud/server#45505 (comment)

did that solve your issue then mate?

from nextcloud-snap.

@sbe-arg any feedback here mate?

from nextcloud-snap.

Not yet I'm planning on setting up a fresh instance and install the social app in a day or 2 I'm hammered with work at the moment.

from nextcloud-snap.

The only update I have is that the nodeinfo error cleared with the nc29 release but webfinger remains

from nextcloud-snap.

After upgrade to 29.0.0 message about webfinger comes back, 29.0.3 did not resolves problem
My Apache with sub-folder installation have necessary .htaccess records

But response to curl request:
{"message":"webfinger not supported"}

take me to essential question — which service must answer to this "webfingering" and if I not installed any social services, there is none that must answer?

thanks,
Saules Ieleja

from nextcloud-snap.

@kyrofa or @pachulo please assist

from nextcloud-snap.

@sbe-arg, did you get this sorted mate?

from nextcloud-snap.

Nope I'm just learning to ignore it.

from nextcloud-snap.

@sbe-arg

Nope I'm just learning to ignore it.

😂 good workaround ✔

I cannot confirm this issue on any of my instances. It seems like something upstream. Mentioned in frequent Nextcloud 29 issues but no solution.

@ieleja is asking valid questions which can only be answered upstream I guess? Would you care to mention this upstream?

from nextcloud-snap.

@ieleja, so you're running behind a reverse proxy?

see Hosts & FQDN configuration

now only complaints is about Data directory accessible to internet, what is not true at all:
nextcloud/server#45087 (comment)

not sure, but that's upstream right?

from nextcloud-snap.

How is this completed?

from nextcloud-snap.