Replies: 3 comments 4 replies
-
What There's no need to involve both Apache and |
Beta Was this translation helpful? Give feedback.
-
if you want to reach your server on an external IP, you'll also need to listen to not 127.0.0.1 but to that IP (or 0.0.0.0 if you only have one) |
Beta Was this translation helpful? Give feedback.
-
Thanks for everyone's input. i finally got it working properly. just have to polish up the presentation a little more. Just had to configure htaccess like i thought. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
OK I used the wasm-setup and wasm-build scripts to compile my application on a remote http server instance. It all but manages to actually be accessible on the internet. on the website it shows a


Forbidden
access restriction where the module should load. I set up firewall-cmd to allow the port though and also specified to listen on port 4000 in httpd.conf. I'm running out of relevant documentation to draw from but everything on the backend seems to be building correctly. I don't know if it's the system's internal configuration or apache's which is preventing it from loading. Has anyone else gotten this to work? If so, how? Thanks in advance.Beta Was this translation helpful? Give feedback.
All reactions