Stuck in configuration process > Checking your system for compatibility #192

New issue

Closed

opened 2026-02-20 15:16:05 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-20 15:16:05 -05:00

Owner

Originally created by @akerd on GitHub (Oct 6, 2017).

Originally assigned to: @NGPixel on GitHub.

Actual behavior

After launching the command

node wiki start 80

and opening localhost at port 80 I am able to see the welcome page and start the configuration process, but it hangs with message "Checking your system for compatibility..." and I have no idea why.

Is it possible to understand the reason why the system check is not able to go on?

I tried to use also the default port 3000 but same problem.

Steps to reproduce the behavior

Windows Server 2016 behind corporate proxy

I installed the pre-requisites:

Node.js 6.11.4
Mongo DB 3.4.9
Git 2.14.2

Powershell install script completed successfully.
I run the command "node wiki configure 80" and launched Internet Explorer 11 to connect to localhost.

Originally created by @akerd on GitHub (Oct 6, 2017). Originally assigned to: @NGPixel on GitHub. ### Actual behavior After launching the command `node wiki start 80` and opening localhost at port 80 I am able to see the welcome page and start the configuration process, but it hangs with message "Checking your system for compatibility..." and I have no idea why. Is it possible to understand the reason why the system check is not able to go on? I tried to use also the default port 3000 but same problem. ### Steps to reproduce the behavior Windows Server 2016 behind corporate proxy I installed the pre-requisites: - Node.js 6.11.4 - Mongo DB 3.4.9 - Git 2.14.2 Powershell install script completed successfully. I run the command "node wiki configure 80" and launched Internet Explorer 11 to connect to localhost.

deekerman

2026-02-20 15:16:05 -05:00

closed this issue
added the
deferred
label

deekerman commented

2026-02-20 15:16:08 -05:00

Author

Owner

@Modest-as commented on GitHub (Oct 6, 2017):

Hi,

I've noticed this behavior today myself. I was also using IE... Tried with firefox and it worked like a charm. Anyway, I hope this comment will make it easier to replicate.

@Modest-as commented on GitHub (Oct 6, 2017): Hi, I've noticed this behavior today myself. I was also using IE... Tried with firefox and it worked like a charm. Anyway, I hope this comment will make it easier to replicate.

deekerman commented

2026-02-20 15:16:08 -05:00

Author

Owner

@NGPixel commented on GitHub (Oct 7, 2017):

This will be fixed in 2.0.

As a workaround for 1.x, avoid using IE for setting up Wiki.js.

@NGPixel commented on GitHub (Oct 7, 2017): This will be fixed in 2.0. As a workaround for 1.x, avoid using IE for setting up Wiki.js.

deekerman commented

2026-02-20 15:16:08 -05:00

Author

Owner