Ray, I would take the assumption that you restarted/reloaded apache after changing the proxy settings. But could you please confirm? :-)

If yes, then I would handover to Tom, as it would more look like an ubooquity issue.

However note that on my side I have the "bypass single root folder" setting active in ubooquity and working like a charm.

Now that it works, can you re-active this ubooquity settings, check the results & advise?

Compared to mine, I miss a "SSLProxyEngine on" in yours. Could you try?

Which would fit with your symptom, isn't-it? :-)

If that does not help, try also to add a reverse proxy prefix:

- in ubooquity admin panel > advanced (mine is "comics")

- in your proxy settings, to reach something like:

ProxyPass /comics http://192.168.0.1:2202/comics

ProxyPassReverse /comics http://192.168.0.1:2202/comics

(I remember some tricky nasty stuff about ending "/" added or missing...)

Well... Then, from the old preferences.xml, I extracted the user list, in the form:

<user>

           <name>USER_1</name

           <passwordHash>HASH_1</passwordHash>

</user>

<user>

           <name>USER_2</name>

           <passwordHash>HASH_2</passwordHash>

</user>

In the new preferences.json, I copy-pasted the former user settings in the section 

 "users" : [ {

    "name" : "USER_1",

    "passwordHash" : "HASH_1"

  }, {

     "name" : "USER_2",

    "passwordHash" : "HASH_2"

  } ],

That enough to re-recreate the previously defined users.

I had a limited number of users therefore could do it by hand. For a bigger user db, would be a pain in the %%% ;-)

If you want to set the permissions for the re-recreated users, then for each "pathString" above the "users" section, you have to complete like this:

"userName" : [ "USER_1", "USER_2" ]

Thanks for the help Tom.

I still believe that for the public release you should propose an automatic mean to transfer the old settings db to the new one. Based on what I saw it seems it be achievable ;-)

Otherwise this will limit the penetration rate of v2.

you said yes, and did it ! 😀

Hi,

Not exactly the same need but a related one: I'd like the migration from 1.x to 2.x to be in position to migrate the users definition automatically. Otherwise, as all db are restarted from scratch, you just loose all users and need to redefine them on by one, but then you change their pwd, which is leading to frustration...

Tom, can you evaluate?

Thanks

I remember a previously answered related request in 1.x ;-)

The glitch in ubooquity is due to something else. Going to be fixed in 2.0.3. See thread posted above. Duplicated entry to me...

Hi,

I would expert proxy settings more than ubooquity here.

I run 2.0.x since weeks behind apache as proxy (WAN access via https, proxy on LAN via http) and everything runs well.

Which proxy do you use ? Was it working before with v1.x?

Then it's too much for me to help. Sorry...

obvious priorities! Félicitations! :-)