When I download the NextCloud app and put in my server name. When I try to connect I get an error ACCESS FORBBIDEN - State token does not match.
Has anyone a resolution for this issue?
Please fill out support template you seem to have overlooked.
We don’t even known which client app you’re referring to (there are several) let alone the versions involved, etc.
Also, what happens when you log into the Web UI directly of your Server?
Dows the same address work in the browser?
Well here is the weird thing, I put in just the domain and it finally worked.
Not, http://yourdomain.com or www.yourdomain.com. Just yourdomain.com and it started working.
1 Like
First inquiry - No I didn’t overlook it, thanks for assuming.
Second inquiry - when I search NextCloud in the app store, only one comes up. But thanks for the input.
Third inquiry - When I put ONLY the domain, it started working. I will chalk that up to lack of input. Because the placeholder clearly states put your server as
https://yourdomain.com. When case in point it is simply yourdomain.com. No https or www.
Cheers
This is definitely not a general issue with the client, but almost certainly has something to do with how your server is configured, i.e. for https to work, your server obviously needs to offer https.
www is a subdomain, just like cloud.yourdomain.com or blog.yourdomain.com or something.yourdomain.com are subdomains. Either your server and DNS are configured to serve Nextcloud through such a subdomain or not. If they are, it will work, if they are not, it won’t.
Then there is something wrong with your browser or you in general. Yes my server does offer https and my domain does have an active SSL and guess what IT DOES WORK. Absolutely none of what you just said makes any sense. You need to re-read what I said and then take foot out of mouth. Just because you don’t put https or www in front of your domain, does not mean your server doesn’t have or offer it.
I’m not the one asking for help here…
For me, the client works either way. If I don’t put anything in front of it it works and redirects to https, if I put http in front of it it works and redirects to https, if I put https in front of it it also works. So this is definitely not a general issue with the client.
Browsers may behave differently as they usually prefer https these days, so regardless of whether you put http, https, or nothing in front of it, it will most likely always connect via https (assuming your server offers https), even if there is no http-to-https redirection configured on the web server.
Glad we can rule that out, we could have done that sooner if you had answerd the question in post #3
I had a bit of a hard time following your posts as well, as you seem to be confusing different things, which I tried to clear up in my post.
No, but it could have been a possible explanation for why it works without anything in front of the URL, but doesn’t work with https in front of it. And again, www has nothing to do with whether it works with http or https in front of it. www is just a subdomain, and if that subdomain isn’t configured on the webserver, in Nextcloud and in DNS, it will never ever work.
Yep that’s exactley what I’m going to do now… Good luck.
Bye Felicia!
it did work, thanks. without https:// . just with the domain.