Nextcloud doesn't recognize authorized users

[medicineman25]

I seem to be having issues with the Nextcloud plugin.

I've just installed it through the official plugin library and I cannot access the dashboard despite having added my local machine's IP address.

Here is the error:

Here is my config file:

My IP address is 10.0.30.10, nextcloud is 10.0.20.90.

According to the documentation, this is all I need to do. I've also restarted the jail in case it needs to pickup the config on change.

Why is this not working?

 

[medicineman25]

According to this thread I needed to add the address of the jail. This did work and I can now access the dashboard.

Why is this not done by default?

Please, for the love of God... either support the plugins properly or just remove them. It's beyond a joke at this point how unstable and unreliable they have become.

Raising a ticket to have that actioned. It's simply unacceptable to lead the user on like this.

 

[morganL]

Glad that it worked...
The DHCP Jail version is automated.. https://www.truenas.com/docs/core/solutions/integrations/nextcloud/
If an IP address is allocated to the jail.... I don't know there is a secure way of communicating that to the App.
If no security is OK... there would be alternatives.
I'd agree that documenting that in the solutions page would be useful. Would that be acceptable?

 

[medicineman25]

Glad that it worked...
The DHCP Jail version is automated.. https://www.truenas.com/docs/core/solutions/integrations/nextcloud/
If an IP address is allocated to the jail.... I don't know there is a secure way of communicating that to the App.
If no security is OK... there would be alternatives.
I'd agree that documenting that in the solutions page would be useful. Would that be acceptable?

Sure, documentation would be a good first step.

I understand there are going to be limitations and hiccups but I guess I'm just beyond the point of reasonable frustration with the "official" plugins. Especially after all this time and branding hype. They and the community plugins have wasted so much of my time. The only ones to ever actually work are Plex and Nextcloud... and even then...

I would rather they just be removed for the sanity of all users.

In fairness, manually config'd jails have always been great. I think it would be best to just focus your energy on documenting that approach, rather than hoping to align every edge case to jails you cannot reasonably hope to support.

I've raised the ticket on your github and hope you will make the right decision.

 

[morganL]

Sure, documentation would be a good first step.

I understand there are going to be limitations and hiccups but I guess I'm just beyond the point of reasonable frustration with the "official" plugins. Especially after all this time and branding hype. They and the community plugins have wasted so much of my time. The only ones to ever actually work are Plex and Nextcloud... and even then...

I would rather they just be removed for the sanity of all users.

In fairness, manually config'd jails have always been great. I think it would be best to just focus your energy on documenting that approach, rather than hoping to align every edge case to jails you cannot reasonably hope to support.

I've raised the ticket on your github and hope you will make the right decision.

If you prefer jails please, use them... they give maximum flexibility and control.

The plugins are widely used and designed for simplicity. We' agree that it's still possible to have configuration issues like the one you described. In this case, I'd agree that documentation could/should be better.

Given the wide range of apps and configurations, we do rely on community testing and feedback... like yours.

 

[medicineman25]

If you prefer jails please, use them... they give maximum flexibility and control.

The plugins are widely used and designed for simplicity. We' agree that it's still possible to have configuration issues like the one you described. In this case, I'd agree that documentation could/should be better.

Given the wide range of apps and configurations, we do rely on community testing and feedback... like yours.

It's really disappointing that you can't see that as a reason to ditch support. My use case is not considered in the 'wide range'. DHCP v static is a very basic consideration within this scenario.

So either it was ignored, not great. Not considered, also not great. Or considered but deemed fine. Definitely not great.

From my perspective you're falling victim to the sunk cost fallacy. You'll need to think more radically than that to become the best option in the market.

Anyway thanks for taking the time, I appreciate a direct line to devs.

 

[morganL]

It's really disappointing that you can't see that as a reason to ditch support. My use case is not considered in the 'wide range'. DHCP v static is a very basic consideration within this scenario.

So either it was ignored, not great. Not considered, also not great. Or considered but deemed fine. Definitely not great.

From my perspective you're falling victim to the sunk cost fallacy. You'll need to think more radically than that to become the best option in the market.

Anyway thanks for taking the time, I appreciate a direct line to devs.

I think the issue is NAT (host IP address) vs separate IP address (DHCP or static)

With a seperate IP address, the Nextcloud application needs a security/configuration change, that needs to be better documented.

Isn't that a reasonable summary?

 

[medicineman25]

Yep, that's correct.

Although now there is another issue where setting the username and password is never prompted, possible because of this issue.

Resetting with:

su -m www -c 'php /usr/local/www/nextcloud/occ user:resetpassword root'

...doesn't work because there is no 'root' or 'admin' user ...

All I get is:

"User does not exist"

 

[ddaenen1]

Yep, that's correct.

Although now there is another issue where setting the username and password is never prompted, possible because of this issue.

Resetting with:

su -m www -c 'php /usr/local/www/nextcloud/occ user:resetpassword root'

...doesn't work because there is no 'root' or 'admin' user ...

All I get is:

the default user and pw is in the post install notes that you can find in the plugin at the bottom, have you checked this?

 

[medicineman25]

the default user and pw is in the post install notes that you can find in the plugin at the bottom, have you checked this?

View attachment 51299

Confirmed the username and password are in the post install notes.