UNABLE TO ACCESS MESHCENTRAL SERVER WEBUI

[mtran-88]

Hi, I am having issues with accessing my meshcentral server using webui. When I've tried to user the meshcentral url, it times out and gives an error message of 'Cant reach the page'. I've run Letsdebug, and it is ok. I am at a lost to what happened. Please see the debug logs below. Thanks in advance for your time.

C:\mc>node node_modules/meshcentral --debug
MAIN: Core module windows-amt is 635517 bytes.
MAIN: Core module linux-amt is 576624 bytes.
MAIN: Core module linux-noamt is 476088 bytes.
MAIN: Core module windows-recovery is 137782 bytes.
MAIN: Core module linux-recovery is 82170 bytes.
MAIN: Core module windows-agentrecovery is 61977 bytes.
MAIN: Core module linux-agentrecovery is 6365 bytes.
MAIN: Core module windows-tiny is 6305 bytes.
MAIN: Core module linux-tiny is 6305 bytes.
MeshCentral HTTP redirection server running on port 80.
AUTHLOG: Server listening on 0.0.0.0 port 80.
CERT: LE: Getting certs from local store (Production)
CERT: LE: Reading certificate files
CERT: LE: Setting LE cert for default domain.
MeshCentral v1.1.38, Hybrid (LAN + WAN) mode.
DISPATCH: AddEventDispatch [ 'server-shareremove' ]
DISPATCH: AddEventDispatch [ '' ]
DISPATCH: DispatchEvent [ '' ]
MAIN: Server started
MeshCentral Intel(R) AMT server running on meshcentral.xxx.com:4433.
AUTHLOG: Server listening on 0.0.0.0 port 4433.
HTTPS: Server listening on 0.0.0.0 port 443.
MeshCentral HTTPS server running on meshcentral.xxx.com:443.
HTTPHEADERS: GET /agent.ashx/.websocket {
host: 'meshcentral.xxx.com',
upgrade: 'websocket',
connection: 'Upgrade',
'sec-websocket-key': '7IcLZJ60Sf6deVtzlRuqLD==',
'sec-websocket-version': '13'
}

MPSCMD: --> KEEPALIVE_REQUEST
MPSCMD: <-- KEEPALIVE_REPLY 0
MPSCMD: --> KEEPALIVE_REQUEST
MPSCMD: <-- KEEPALIVE_REPLY 0
MPSCMD: --> KEEPALIVE_REQUEST
MPSCMD: <-- KEEPALIVE_REPLY 0
MPSCMD: --> KEEPALIVE_REQUEST
MPSCMD: <-- KEEPALIVE_REPLY 0
MPSCMD: --> KEEPALIVE_REQUEST
MPSCMD: <-- KEEPALIVE_REPLY 0
MPSCMD: --> KEEPALIVE_REQUEST
MPSCMD: <-- KEEPALIVE_REPLY 0
MPSCMD: --> KEEPALIVE_REQUEST
MPSCMD: <-- KEEPALIVE_REPLY 0
MPSCMD: --> KEEPALIVE_REQUEST
MPSCMD: <-- KEEPALIVE_REPLY 0
MPSCMD: --> KEEPALIVE_REQUEST
MPSCMD: <-- KEEPALIVE_REPLY 0
DISPATCH: DispatchEvent [ '*' ]
MPSCMD: --> KEEPALIVE_REQUEST
MPSCMD: <-- KEEPALIVE_REPLY 0
Server Ctrl-C exit...

[PathfinderNetworks]

You'll need to post your config.json (with any sensitive info commented out) so we can help troubleshoot. Also, have you tried accessing it from the local, LAN IP address of the server?

[mtran-88]

Hi, I have tried the local IP address of the server, and can get to the login page. After logging in with password and token, I get this error message.

[si458]

You need to access ur meshcentral server using the dns value u set in cert to avoid the invalid origin error

[mtran-88]

Hi Simon! Happy New Year! Hope you are having a great start to 2025!

I did try the DNS name, but get nowhere with it. I am perplexed on the reason. Pathfinder asked me to try the LAN IP address so I am responding to his query. Let me know your thoughts on why I cannot access the server using the DNS name even though Lets debug passed.

[si458]

Well, I've just visited ur login page, no problem?
Loads up straight away.
Is the meshcentral hosted in the cloud or onsite?
If onsite have u checked ur firewall for reverse nat so ur dns name works internally (hairpin nat in mikrotik terms)?

[mtran-88]

oh, awesome! Thanks for trying that! I will look into it further!

[PathfinderNetworks]

I'm able to see your login page for MeshCentral as well.

[djsejo1]

Hi everyone, I am quite new to this, and I have the same problem that was mentioned above. My scenario is the following, I use nas synology and docker, I have downloaded the ghcr.io/ylianst/meshcentral:latest image and my docker-compose configuration is as follows:

version: '3'
services:
  meshcentral:
    restart: always
    container_name: meshcentral
    image: ghcr.io/ylianst/meshcentral:latest
    ports:
      - 5050:5051 
    environment:
      - HOSTNAME=my ip nas
      - REVERSE_PROXY=true
      - REVERSE_PROXY_TLS_PORT=
      - IFRAME=true
      - ALLOW_NEW_ACCOUNTS=false
      - WEBRTC=false
    volumes:
      - /volume1/docker/meshcentral/data:/opt/meshcentral/meshcentral-data
      - /volume1/docker/meshcentral/user_files:/opt/meshcentral/meshcentral-files

my config.json file is the following:

{
  "$schema": "https://raw.githubusercontent.com/Ylianst/MeshCentral/master/meshcentral-config-schema.json",
  "settings": {
    "plugins":{"enabled": false},
    "_mongoDb": null,
    "cert": "meshcentral.mydomain.es",
    "_WANonly": true,
    "_LANonly": true,
    "sessionKey": "myid",
    "port": 5050,
    "_aliasPort": 443,
    "redirPort": 5051,
    "_redirAliasPort": 80,
    "AgentPong": 300,
    "TLSOffload": false,
    "SelfUpdate": false,
    "AllowFraming": false,
    "WebRTC": false
  },
  "domains": {
    "": {
      "_title": "AG-INFOR",
      "userCreation": false,
      "_title2": "AG-INFOR",
      "minify": false,
      "NewAccounts": true,
      "localSessionRecording": true,
      "_userNameIsEmail": true,
      "_certUrl": "meshcentral.mydomain.es",
      "trustedDomains": "meshcentral.mydomain.es",
      "welcome": "Welcome to AG-INFOR - Support",
      "icon": "meshcentral-web/logo.png"
    }
  },
  "_letsencrypt": {
    "__comment__": "Requires NodeJS 8.x or better, Go to https://letsdebug.net/ first before>",
    "_email": "[email protected]",
    "_names": "meshcentral.mydomain.es",
    "production": false
  }
}

The tests that I have carried out or have been able to observe are the following:
I download the image, run docker-compose and log in with the nas IP and port 5050, the main page or meshcentral base appears, I create a user and when I log in with him the error appears

Then I go to the config.json file and put the configuration that I gave you previously, but nothing changes, I still have the same error.
I also did the thing of configuring the reverse proxy from the nas synology to be able to access it from outside.
I'm telling you all this because there was a time when I did a test and everything worked the first time, I don't know if it was luck or not, but it makes me angry because I don't remember how I did it and I know it worked since I still have the agent and the configuration where it connected but it was only a test and when I deleted and tried again to have meshcentral with the ports and configuration that I wanted I have never been able to do it again and I don't know what to do honestly, as I say I'm no expert, but I know that it worked for me once, with my domain port 5111 at that time and the reverse proxy

thanks in advance to anyone who can help me

[djsejo1]

I have modified my docker-compose, I have set the ports as you told me correctly, and added my domain to cert but nothing at all, I do not have access either by nas IP + port or by domain, (the domain works since I have it pointed to the public IP and it loads the default synology page)

[si458]

u have set it up wrong again
port should be set to a port you want to access via the web ui and ur agents to access
redirport is just the http port which diverts to the https port
so set port: 443 and redirport: 80
then you also need to set aliasPort: 5050
this tells meshcentral run on port 80+443 BUT tell the outside world to talk to me on port 5050 because im a container or behind a firewall, etc
then simply portforward 80 to 80 and portforward 5050 to 443 in your NAS UI
also remove certurl as thats only used if you have a reverse proxy setup like nginx/traefik/apache/etc...

[djsejo1]

I think I may not explain well and I repeat I am not an expert in this, what I want to do is simple or at least that's what I thought but I see that it is not. I simply want to have meshcentral in docker on my nas, and be able to access it both on the local network and if I am outside, for this I have my own domain and I have created a subdomain and pointed it to my public IP, so far everything is perfect. Now you say that in port I must put the port that I want to use, in my case as I have both 80 and 443 busy that is why I am trying to use 5050 and 5051 so I understand that in port it should be 5050 but I really don't know what's wrong or what I'm doing wrong, I just want meshcentral to work by accessing https://meshcentral.midominio.es without the port coming out (which is why I mentioned the reverse proxy), excuse my lack of knowledge on this and thanks again

[djsejo1]

Hello again, I have finally managed to access both the local network and from outside, I leave you a screenshot of how I currently have it in case it helps someone else, on the other hand I am still trying now with the reverse proxy so that the port does not appear, if I succeed I will also upload a screenshot, thanks for the help @si458

[djsejo1]

I have finally achieved what I wanted, having meshcentral and being able to access it from outside the local network with meshcentral.mydomain.es without the need for the port to appear. I attach here some screenshots of the configuration I made of the reverse proxy in synology nas and in the config.json file I changed what was marked in yellow from 5051 to 80 and from false to true, I hope it helps you. greetings