We can not connect to mattermost either with personal access token with login and password

[AirMarty]

Hi, thank you for your work. We use nextcloud-OAI (Nextcloud Hub 6 (27.1.0)) We try to use your integration but we can not connect account With personal access token -> "Invalid Access Token" With login and password -> "Invalid login/password"

May be we dont properly setup the integration or the configuration or make some mistake ?

I try to check chrome dev tools but i'm not cconfident with de nextcloud API.

Tell us which kind of information (and where to get it in nextcloud) and anykind of details, information, configuration, etc that will help.

THX

[devillemereuil]

I have exactly the same issue on a Yunohost installation with both Nextcloud and Mattermost apps installed!

[devillemereuil]

Relevant line in the log I suppose:

{"reqId":"GGGGGGGGGGGG","level":2,"time":"2024-01-04T19:42:54+00:00","remoteAddr":"XX.XX.XX.XX","user":"username","app":"integration_mattermost","method":"PUT","url":"/apps/integration_mattermost/config","message":"Mattermost login error : Host violates local access rules","userAgent":"Mozilla/5.0 (X11; Linux x86_64; rv:121.0) Gecko/20100101 Firefox/121.0","version":"27.1.4.1","data":{"app":"integration_mattermost"}}

EDIT: Sorry, wrong line.

[devillemereuil]

Seems like this line is needed in config.php :

'allow_local_remote_servers' => true,

This solves the problem for me.

[p3k]

Seems like this line is needed in config.php :

'allow_local_remote_servers' => true,

This solves the problem for me.

I have this exact line in my config.php and it does not solve the issue.

[kyteinsky]

@AirMarty Please post the web browser's console error and the response of the failing requests from the Network tab.
Also include nextcloud server logs. I would suggest to upgrade to NC 28 and use the updated app before that.

@devillemereuil @p3k allow_local_remote_servers is a nextcloud config key that allows local server connections. It is dependent on your mattermost setup and needs to be done only for local setups of mattermost.

[p3k]

@kyteinsky I am using a local setup of mattermost.

[kyteinsky]

@p3k Can you furnish me with some browser's logs, Network tab responses and NC server logs? And update the NC server and app to their latest versions if you can.

[AirMarty]

@AirMarty Please post the web browser's console error and the response of the failing requests from the Network tab. Also include nextcloud server logs. I would suggest to upgrade to NC 28 and use the updated app before that.

@devillemereuil @p3k allow_local_remote_servers is a nextcloud config key that allows local server connections. It is dependent on your mattermost setup and needs to be done only for local setups of mattermost.

Ok why not but where I can find the nextcloud server logs because as far as I know there's lot of container in the Nextcloud AIO installation. We've laready try to find some readable LOGs among the amount of services but there's too many with few support documentation.

I'll post here the console log from browser next time I'll test it !

[kyteinsky]

@AirMarty It is /var/www/html/data/nextcloud.log this file inside the nextcloud container.
Post the output to docker ps in case you can't find the nextcloud container.

[p3k]

@p3k Can you furnish me with some browser's logs, Network tab responses and NC server logs? And update the NC server and app to their latest versions if you can.

so I wanted to provide the server logs, which needed a closer look at the issue again, and found it is a firewall issue after all – doh!

both, nextcloud and mattermost, run in an LXC container each, proxied by an apache in another container, all behind a single IP address routed via NAT/iptables… neither nextcloud, nor mattermost could connect to their own or the other‘s public URL, and thus connection always failed.

for now I added entries for the public hostnames pointing to the internal IPs (the LXC ones behind the firewall) to /etc/hosts and this got it working.

of course the right way to solve this is fixing the NAT, but this is another story.

thanks for the rubberducking, @kyteinsky 🐤 😉