[MGNLDEMO-198] 404 when installing Magnolia Created: 29/Nov/16 Updated: 07/Mar/21 |
|
| Status: | Open |
| Project: | Magnolia Demo Projects |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Low |
| Reporter: | Martin Schmid | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | 0d | ||
| Environment: |
OS X 10.11.6 |
||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
I followed the instructions on the “Hello Magnolia” support page. However, when I want to navigate to http://localhost:8080/magnoliaAuthor/.magnolia/admincentral, I get a 404. Steps to reproduce
Actual result404 is returned for http://localhost:8080/magnoliaAuthor/.magnolia/admincentral Expected resultInstallation can be started Additional information$ ls -a magnolia-5.5/apache-tomcat-8.5.5/webapps/magnoliaAuthor/ lists
A folder “.magnolia” is missing, indeed. |
| Comments |
| Comment by Ervin Vystup [ 30/Nov/16 ] |
|
Hello Michael, During the first installation you should be redirected to the http://localhost:8080/magnoliaAuthor/.magnolia/installer page after clicking on “Run the Web update on the author instance”. Please, could you try to use this URL and tell me what will happen? You should see a page like this one: But as it is not the typical behavior, please send me the log file (/apache-tomcat-8.5.5/logs/catalina.out) for me to see where a problem can be. An error must have occurred there which created this problem. Please also ask your contact person from the Magnolia sales team to create a support account for you so that we could move this ticket there. Best regards, |
| Comment by Martin Schmid [ 01/Dec/16 ] |
|
Also http://localhost:8080/magnoliaAuthor/.magnolia/installer returns a 404. In the catalina log file that you pointed out, I found:
I found out that tomcat was using /Library/Java/JavaVirtualMachines/jdk1.7.0_71.jdk/Contents/Home/jre as java home. Once I switched to /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home, where Java 8 is installed, it all worked fine. Thank you for your help.
I am not in contact with the sales team. |
| Comment by jeffry [ 24/May/17 ] |
|
hi , i have the magnolia CE: magnolia-5.5.4 [latest at this moment] error i saw in the log: Solution: |
| Comment by jeffry [ 24/May/17 ] |
|
however, stop the server. exit the cmd promt (I would)
|
| Comment by Martin Schmid [ 24/May/17 ] |
|
Hi jeffry, that exactly the same cause as I described in https://jira.magnolia-cms.com/browse/MGNLDEMO-198?focusedCommentId=135699&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-135699 this ticket is |
| Comment by alaa salameh [ 25/Jan/21 ] |
|
I had the same issue , its because i have JAVA_HOME points to java 15 , i fixed that setting JAVA_HOME to java 8 in magnolia-control.bat file.
try add this line to manolia-control.bat SET JAVA_HOME="your java 8 installed location" |
| Comment by Mikhail Dosov [ 07/Mar/21 ] |
|
I had exctly the same issue. Win 10 64 bit, JDK 15, JAVA_HOME= JDK 15. I've tried to install magnolia by this https://docs.magnolia-cms.com/product-docs/Getting-started-with-Magnolia/Installing-Magnolia/Installing-Magnolia-through-npm-CLI.html All was fine up to https://docs.magnolia-cms.com/product-docs/Getting-started-with-Magnolia/Installing-Magnolia/Installing-Magnolia-through-npm-CLI.html#_logging_into_the_author_instance Then I tried to open "Run the Web update on the author instance" in http://localhost:8080 I've got 404 error. Follow alsalameh102 I download JDK 8 and change JAVA_HOME to JDK 8. It works!
|