Glitches With Custom Port Change #819
Locked
LordRalex
announced in
Legacy - Support
Replies: 3 comments 1 reply
-
LordRalex wrote at Jul 19 2018 21:22:01 UTC: You have to update your daemon to look for this new port. /srv/pufferd/config.json |
Beta Was this translation helpful? Give feedback.
0 replies
-
GTextreme wrote at Jul 19 2018 21:22:01 UTC: Can I have an example of this? My current config.json only has mysql config in it. |
Beta Was this translation helpful? Give feedback.
1 reply
-
GTextreme wrote at Jul 19 2018 21:22:01 UTC: For some reason, pufferd was in the etc folder and not srv. I changed the file and everything works. Thank you. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
GTextreme wrote at Jul 19 2018 21:22:01 UTC:
I installed this with nginx. The Sites-enabled pufferpanel.conf has "listen 81;" The PufferPanel Master URL is set with the extension ":81/". The website loads completely, but no actions work, the file manager shows nothing. The Console is also blank and reports server errors whenever an action is clicked (Start, install, stop, etc). Is there another reference I am missing? I cannot use port 80 as another computer is hosting that port publicly on the same network.
Beta Was this translation helpful? Give feedback.
All reactions