Hi. After upgrading to Enonic XP 6.9.1 we’ve encountered some issues with the virtual host configuration. We get 404 on all resources in the Enonic admin panel after logging in.
This is what we have used so far in our com.enonic.xp.web.vhost file:
It is problable that it fails because it does not find the corresponding Vhost mapping as you mentionned.
Do you have access to the logs?
If you do, do you see logs similar to: “Virtual host mapping could not be resolved:”
It should describe the host and path it was looking for
Yes, I forgot to mention what’s in the log. Here you go:
13:54:44.990 WARN c.e.x.w.vhost.impl.VirtualHostFilter - Virtual host mapping could not be resolved: d-114-270-089/admin/assets/6.9.1/common/styles/_all.css
13:54:44.990 WARN c.e.x.w.vhost.impl.VirtualHostFilter - Virtual host mapping could not be resolved: d-114-270-089/admin/assets/6.9.1/common/styles/_home.css
13:54:44.990 WARN c.e.x.w.vhost.impl.VirtualHostFilter - Virtual host mapping could not be resolved: d-114-270-089/admin/assets/6.9.1/common/lib/_all.js
13:54:44.990 WARN c.e.x.w.vhost.impl.VirtualHostFilter - Virtual host mapping could not be resolved: d-114-270-089/admin/assets/6.9.1/common/js/_all.js
13:54:44.990 WARN c.e.x.w.vhost.impl.VirtualHostFilter - Virtual host mapping could not be resolved: d-114-270-089/admin/assets/6.9.1/apps/home/js/_all.js
13:54:45.021 WARN c.e.x.w.vhost.impl.VirtualHostFilter - Virtual host mapping could not be resolved: d-114-270-089/admin/common/images/background-1920.jpg
Do I need to specifically set up additional vhost-mappings in addition to the ones I already posted?
No finally, I do not think it is linked to a vhost mapping missing.
There seems to be a bug in the way admin assets are rendered in 6.9 when the “/admin” is renamed (in your case to “/pilot/admin”)
I will forward the problem and it should be fixed in a 6.9.2
If you can, you could map “/admin” to “/admin” to unblock the situation for now
The fact that the redirection “http://xp.no” -> “http://xp.no/admin/tool” you mention does not work anymore is done on purpose.
It is now stricter. If the virtual hosting is enabled, Enonic XP will not serve a resource accessed outside of a VHost mapping (like “http://xp.no” in your case)
We have fixed three issues and were hoping to release 6.9.2 today, but testing revealed a critical bug.
The bug has been fixed, and we are now testing again. Unless we find more bugs, 6.9.2 should be out today, but we can not make any guarantees. We must make sure there are no other critical bugs.
Piggy-backing this thread since we have some similiar issues regarding the vhost-configuration.
Enonic Version: 6.9.2
We are trying to reach: <host>/admin/rest/security/principals/<userkey>?memberships=true from /admin but this results to a 404.
A user has been created and is visible from /admin in Users. However, when I try to edit the recently created user I get the notification-error: Principal [<userkey>] was not found.
I suspect that is something to do with the vhost-configuration, but I’m not sure how I should proceed.
I do not think it is linked to Vhost. It is a 404 yes but with an error message actually generated by Enonic XP.
I suppose it is linked to the user key that you pass. It should have the following format: “user:[userstore]:[username]”
Example for super user:
[host]/admin/rest/security/principals/user:system:su?memberships=true
If the problem persist: Does it contains a capital letter or a special character?