Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: No default engine was specified and no extension was provided.

See original GitHub issue

Issue Summary

can’t access admin home (/ghost) after fresh install 1.4.0 detail error message (it is printed in web browser):

Error: No default engine was specified and no extension was provided.
    at new View (/home/seungha/ghost-test/versions/1.4.0/node_modules/express/lib/view.js:62:11)
    at EventEmitter.render (/home/seungha/ghost-test/versions/1.4.0/node_modules/express/lib/application.js:570:12)
    at ServerResponse.render (/home/seungha/ghost-test/versions/1.4.0/node_modules/express/lib/response.js:971:7)
    at HTMLErrorRender (/home/seungha/ghost-test/versions/1.4.0/core/server/middleware/error-handler.js:86:9)
    at Layer.handle_error (/home/seungha/ghost-test/versions/1.4.0/node_modules/express/lib/router/layer.js:71:5)
    at trim_prefix (/home/seungha/ghost-test/versions/1.4.0/node_modules/express/lib/router/index.js:315:13)
    at /home/seungha/ghost-test/versions/1.4.0/node_modules/express/lib/router/index.js:284:7
    at Function.process_params (/home/seungha/ghost-test/versions/1.4.0/node_modules/express/lib/router/index.js:335:12)
    at next (/home/seungha/ghost-test/versions/1.4.0/node_modules/express/lib/router/index.js:275:10)
    at prepareError (/home/seungha/ghost-test/versions/1.4.0/core/server/middleware/error-handler.js:58:5)
    at Layer.handle_error (/home/seungha/ghost-test/versions/1.4.0/node_modules/express/lib/router/layer.js:71:5)
    at trim_prefix (/home/seungha/ghost-test/versions/1.4.0/node_modules/express/lib/router/index.js:315:13)
    at /home/seungha/ghost-test/versions/1.4.0/node_modules/express/lib/router/index.js:284:7
    at Function.process_params (/home/seungha/ghost-test/versions/1.4.0/node_modules/express/lib/router/index.js:335:12)
    at next (/home/seungha/ghost-test/versions/1.4.0/node_modules/express/lib/router/index.js:275:10)
    at Layer.handle_error (/home/seungha/ghost-test/versions/1.4.0/node_modules/express/lib/router/layer.js:67:12)
    at trim_prefix (/home/seungha/ghost-test/versions/1.4.0/node_modules/express/lib/router/index.js:315:13)
    at /home/seungha/ghost-test/versions/1.4.0/node_modules/express/lib/router/index.js:284:7
    at Function.process_params (/home/seungha/ghost-test/versions/1.4.0/node_modules/express/lib/router/index.js:335:12)
    at next (/home/seungha/ghost-test/versions/1.4.0/node_modules/express/lib/router/index.js:275:10)
    at /home/seungha/ghost-test/versions/1.4.0/node_modules/express/lib/response.js:424:7
    at SendStream.onerror (/home/seungha/ghost-test/versions/1.4.0/node_modules/express/lib/response.js:1003:5)

and after I upgraded Ghost from 1.1.0 to 1.4.0, it showed 404 page.

Technical details:

Ghost Version: 1.4.0
Node Version: 6.11.1
Browser/OS: Manjaro
Database: SQLite3

Issue Analytics

State:
Created 6 years ago
Reactions:5
Comments:11 (5 by maintainers)

Top GitHub Comments

10reactions

kirrg001commented, Aug 2, 2017

You can manually sort this out by copying current/core/server/admin/views/default-prod.html to current/core/server/admin/views/default.html and restart Ghost via ghost restart.

2reactions

kirrg001commented, Aug 3, 2017

1.5.0 was released.