Network Error: Value <!DOCTYPE of type java.lang.String cannot be converted to JSONArray

[SimonLefort]

Hello,
I discovered Passman yesterday and I installed it on my Nextcloud 12 instance. It work when I use it from Nextcloud and from the Firefox Add-on but I had a problem.

I took a screenshot of my screen.

Now, I just can connect and It works...

Is it possible that I have this error with a wrong password? I try multiple times, I don't think the password is the problem but it's not very clear...

ps: Thanks for your work! Can I find a roadmap somewhere? Do you plan to support iOS for mobile? :-)

[animalillo]

That error looks like there was a server side error or the data for corrupted on the path. Could you check your server logs around that time?

We don't currently have a roadmap, and we keep improving passman on our free time, which lately had been very little. Hopefully next year we can have some push on the android app and add the encryption part (creating and saving credentials)

[splitt3r]

It happens e.g. if the app is not installed yet on server or the url is wrong and you try to login via android app. I played around a bit today and discoverred the same message.

[animalillo]

interesting, the thing is that the app expects a json response, and if it fails it seems to be displaying the html response.

I might take a look into this, but it's not a big issue. The app should ask if you entered the correct passman address instead of just html.

Also thanks for the report and hope you love passman as much as we do!

[splitt3r]

You are doing a great job 🥇

[SimonLefort]

Thanks for your answers!

I didn't check my server logs but I'll do it when I have a moment.

@splitt3r : In my case, Passman was installed on the server before I test from Android and I use the right adresse (the same works now).

[splitt3r]

Ok, is there any error listed in your server logs?

[SimonLefort]

I couldn't find anything relevant. :-/

[JoergPalmer]

I had the same problem when I unnecessarily had a trailing "/" in the URL. For some reason I'm in the habit of typing URLs like this.
After removing the trailing slash it connected without any further problem.

[bwa-]

I've had the same problem. Found out via the nextcloud.log that what happened was that my android keyboard automagically made the first letter of the URL uppercase which made the 'trusted domain' check fail. Adding that "new" domain in the config.php fixed the problem. Works fine now, thanks!

[cfangmeier]

I also had this problem arise when the server is in the middle of a version upgrade. In my case, I upgraded Nextcloud on my server to version 14 through my package manager, but hadn't yet run the ./occ upgrade step. Once I did that, It worked fine. (Also, just be aware that passman currently requires a hack to work on Nextcloud 14 nextcloud/passman#491 )

[mconway]

This just happened to me - its because I have OTP enabled on my NC instance. You can generate an app password to get around it, if that's your problem at least.

[vwbusguy]

I get this no matter what with the recent passman update (on nc15). It was working fine until the recent passman update yesterday. Now the app no longer connects and just gives this error.

[developerfromjokela]

I can implement code that checks if string response is valid JSON or not.

[vwbusguy]

In my case, it looks like when I upgraded Nextcloud last, Passman was disabled because of the version not supported. When I updated Passman, it did not become re-enabled automatically, which caused the app call to fail presumably with a 404. After I re-enabled Passman, the app began to work again. Perhaps it would be better if the app evaluated the returned status code before attempting to parse the JSON so that it can return a more intuitive error message.

[developerfromjokela]

@vwbusguy So we need code that checks if App is existing on NC server.

[MathieuSchopfer]

I ran into this issue. The problem was a white space " " at then end of the server's url.