Cannot access setup on another port #473
Unanswered
exstntlmsnthrp
asked this question in
Support
Replies: 3 comments
-
Can anyone help with this? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Unfortunately, I can't. I haven't working with Apache for like 10 years. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Not really a helpfull from mine, this is my apache conf, as i rely on
|
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
-
Hello.
I see this discussion section hasn't been active for awhile, so hopefully someone sees this. I installed LinkAce on a network server I have setup. I followed the setup without docker. Everything went well until Step 5.
I do have several other things setup on the server (each with a unique port number) without any problem. Given that Apache recommends using config files instead of htaccess files, I set one up for my LinkAce setup as follows. As I have several other things installed on the server, I did give the LinkAce its own port number. Obviously I did enable it and I also restarted Apache.
linkace.config
I also gave www-data ownership of my linkace directory so there aren't any problems. I should also note that my rewrite and negotiation mods have also been enabled.
However, when I enter my.local.ip.address:61010 or my.local.ip.address:61010/public in my browser, it gives me an unable to connect error. When I nmap my.local.ip.address -p 61010, it is unsuccessful; presumably because linkace is not listening there. Can anyone provide any advice to what is going wrong here? Have I missed something? Is something configured incorrectly?
Any help is greatly appreciated. I really look forward to trying this out!
Beta Was this translation helpful? Give feedback.
All reactions