


Hello,
I have a CQ5 authoring instance that I can no longer access. I was attempting to install a new SSL certificate on the server, and following instructions I found online, I did the following:
3. Install keystore into CQ
a. Copy the keystore file (cqkeystore.keystore) into the cq installation folder (D:\cq\author\crx-quickstart)
b. Create a node under /apps with the following structure
apps (sling:Folder)
system (sling:Folder)
config.author (sling:Folder)
org.apache.felix.http (sling:OsgiConfig)
c. Add the following property to org.apache.felix.http node and save
Name | Type | Value |
---|---|---|
org.apache.felix.https.enable | Boolean | true |
org.osgi.service.http.port | Long | 80 |
org.osgi.service.http.port.secure | Long | 443 |
org.apache.felix.https.nio | Boolean | true |
Once I added the node, changed these properties, and saved, I was no longer able to access my CQ5 instance. Originally the app ran on port 4502, however now trying to access on 4502 gives a 404. Trying to access on port 80, I receive the following error:
I cannot access the development environment within the application to revert this change. I either need to: A, figure out how to edit the files without doing it through the /crx/de path. or B, need to figure out how to access the application.again
Any help is appreciated.
Thanks
Views
Replies
Sign in to like this content
Total Likes
Solved this issue by using the Auto Installer feature. I created a new package containing an '/apps/server/config' folder that effectively overwrote the change I made that disabled my access to the application. By creating an 'install' folder under 'crx-quickstart' and placing my package in that 'install' folder, CQ5 automatically installed my package on the next server startup, which allowed me to access the application again
Views
Replies
Sign in to like this content
Total Likes
seems server is running on 4502. 80 might have used by other webserver. Try to login from http://host:port/crx/explorer/
Views
Replies
Sign in to like this content
Total Likes
Solved this issue by using the Auto Installer feature. I created a new package containing an '/apps/server/config' folder that effectively overwrote the change I made that disabled my access to the application. By creating an 'install' folder under 'crx-quickstart' and placing my package in that 'install' folder, CQ5 automatically installed my package on the next server startup, which allowed me to access the application again
Views
Replies
Sign in to like this content
Total Likes