asked on October 15, 2025
Hi Flexmonster Team,
I’ve successfully installed the Flexmonster Accelerator as a Windows Service on my server. The service is running correctly, and the logs confirm that it’s active on http://localhost:50005.
However, I’m unable to access the Accelerator from outside the server. I’ve already created an inbound rule in Windows Firewall to allow traffic on port 50005, but when I try to reach the service from an external machine (e.g. http://<server-ip>:50005/), the connection fails.
Here’s my current configuration from the .env file:
CONNECTION_STRING=Data Source=********\SQLSERVER2016
PORT=50005
HTTPS=false
CACHE_MEMORY_LIMIT=0
CACHE_ENABLED=true
GZIP=true
ALLOW_ORIGIN=*
WINDOWS_AUTH=false
Could you please confirm whether the Accelerator can be accessed remotely, or if it’s restricted to localhost-only connections? If remote access is supported, please advise how to enable it.
⋅ October 16, 2025
Hello Zain,
Thank you for reaching out to us.
Flexmonster Accelerator can be accessed remotely, as shown in this example with our server running the Accelerator: https://jsfiddle.net/flexmonster/xhrwqbkm/
From your configuration, there are no reasons for potential connection issues, since both CORS and Windows authentication are disabled. The screenshot you have shared also indicates that the Accelerator is up and running.
As a next step, open http://localhost:50005 in a browser or perform a GET request directly on the server. It should display the following message:
Flexmonster Accelerator for Microsoft SSAS
Proxy URL: http://localhost:50005
If that works, try opening this endpoint from a public address on another machine.
If the connection fails, it means that a firewall, network rule, or proxy is still blocking external access, so check those configurations further.
Hope our answer will help you.
Best regards,
Maksym
⋅ October 16, 2025
Why is the proxy URL n/a?
⋅ October 17, 2025
Hello Zain,
Thank you for your reply.
It appears to be a visual bug, which is not critical and does not affect the functionality. The proxy URL displaying as "n/a" corresponds to the same local server address: http://localhost:50005
This is a known issue, and we already have it in our backlog to be addressed in the future.
Best regards,
Maksym
