Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

can't change port number #175

Open
6 of 10 tasks
hchaase opened this issue Mar 19, 2021 · 1 comment
Open
6 of 10 tasks

can't change port number #175

hchaase opened this issue Mar 19, 2021 · 1 comment

Comments

@hchaase
Copy link

hchaase commented Mar 19, 2021

Maybe a bug? (I found a solution for my usecase no help needed)

I upgraded to the newest version and found that It served the wikis on port 8081 instead of the previous 8080.

I tried to correct this in the controlPanel/bob/serversettings/Manual settings and enabling editing. here the ws-server": {
"autoIncrementPort was set to false. I changed all 8081 to 8080 updated settings (and later restarted the wiki) but no changes. It reverted back to 8081.

I solved my problem by changing the port in the settings file: IndexWiki\settings\settings.json. After this the port was changed. But I wonder if it wasn't suppose to do that by changing the port through the wiki? (tried the "admin" bob wiki and in the actual front wiki)


I am running (check any that apply, put an x inside the [ ] to check a box, like this: [x]):

  • Windows
  • OSX
  • Linux
  • Other

and using

  • The nodejs version
  • The single file executable

Before posting I read issue guidelines and:

  • I am using the newest version
  • The answer to my question isn't listed in the documentation or this isn't
    a question
  • This is not a duplicate issue
  • I have not done anything that required me to set acceptance to
    I Will Not Get Tech Support For This
@inmysocks
Copy link
Member

It is supposed to change when you edit it in the wiki, I am seeing the same behavior. I am guessing that it is a problem with how updated settings are saved but I am not sure when I will get a chance to fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants