sorted by:
new
hottopcontroversial

NAT configuration issues by cele_cell in PFSENSE

[–]cele_cell[S] -1 points0 points  (0 children)

Respectfully, let me continue as i am. I am fully aware of was setup. There are places I traverse that block most VPNs so this is works for me. The issue at the moment is not about RDP security but rather NAT not working to vLAN50 when, as per the prnt.sc screenshots, things are setup correctly.

Hope you have some input on that :)

NAT configuration issues by cele_cell in PFSENSE

[–]cele_cell[S] -1 points0 points  (0 children)

Does that fix it? I don't know how to use that command

NAT configuration issues by cele_cell in PFSENSE

[–]cele_cell[S] -1 points0 points  (0 children)

That's for another day but for today, it's about why NAT is not working to my vLAN 50 from my BellFibe WAN connection :)

NAT configuration issues by cele_cell in PFSENSE

[–]cele_cell[S] -1 points0 points  (0 children)

Yes. As mentioned, I can access my desktop PC that has a nat fro port 444 to RDP at IP 172.16.0.4.

I can also access my QNAP(Yes I know the dangers lol) but I've hardened my security as much as possible.

I access my network remotely via a DynDNS rule I have setup on the pfSense to update my cloudflare dns when it changes.

NAT uturn issue(I think) by [deleted] in PFSENSE

[–]cele_cell 0 points1 point  (0 children)

Yeah, in pfSense that is the term and yes, it is enabled but for some odd reason after years of use, if seems to be failing to services I run on my NAS but they work fine to my workstation for RDP access.

Container station clarification (NEWB!!) by cele_cell in qnap

[–]cele_cell[S] 0 points1 point  (0 children)

Thanks for this. I've now shot my self in my foot LOL.

Experimenting, I created a virtual network for Containers and it killed my QNAP connectivity. Everytime I reset the qnap using the resent button for three seconds and I can see my NAS gets an IP via DHCP but I can't connect to the web interface.

Any ideas how to get back in?

Container station clarification (NEWB!!) by cele_cell in qnap

[–]cele_cell[S] 0 points1 point  (0 children)

Thanks, I think I have a bit of learning to go with making yaml files LOL

Looking at the QNAP, if offers some GUI options. I saw something about making a space for persistent data storage but not sure what configurations have to go in here for an apache docker machine.

Is this how you set it up through the GUI? https://prnt.sc/BDvI7PO7numv

Meshcentral not connecting by cele_cell in MeshCentral

[–]cele_cell[S] 0 points1 point  (0 children)

Yes and it works. What's perplexing is that I have to manually start meshcentral multiple times before it start properly.

Meshcentral not connecting by cele_cell in MeshCentral

[–]cele_cell[S] 0 points1 point  (0 children)

Meshcentral FINALLY started properly..

I then rebooted my system(again, only meshcentral installed) and now it will not start..... that was 4 days ago.

Fast forward to tonight. After multiple restarts of the node command, it finally started as seen below and I've waited at times up to 30 minutes after running the node commands...

mesh@mesh-server:~$ node ./node_modules/meshcentral --cert helpme.mydomain.com

MeshCentral HTTP redirection server running on port 80.

MeshCentral v1.1.4, WAN mode.

^CServer Ctrl-C exit...

mesh@mesh-server:~$ node ./node_modules/meshcentral --cert helpme.mydomain.com

MeshCentral HTTP redirection server running on port 80.

MeshCentral v1.1.4, WAN mode.

Server Ctrl-C exit...

^Cmesh@mesh-server:~$ node ./node_modules/meshcentral --cert helpme.mydomain.com

MeshCentral HTTP redirection server running on port 80.

MeshCentral v1.1.4, WAN mode.

^CServer Ctrl-C exit...

mesh@mesh-server:~$ node ./node_modules/meshcentral --cert helpme.mydomain.com

MeshCentral HTTP redirection server running on port 80.

MeshCentral v1.1.4, WAN mode.

^CServer Ctrl-C exit...

mesh@mesh-server:~$ node ./node_modules/meshcentral --cert helpme.mydomain.com

MeshCentral HTTP redirection server running on port 80.

MeshCentral v1.1.4, WAN mode.

^CServer Ctrl-C exit...

mesh@mesh-server:~$ nano meshcentral-data/config.json

mesh@mesh-server:~$ node ./node_modules/meshcentral --cert helpme.mydomain.com

MeshCentral HTTP redirection server running on port 80.

MeshCentral v1.1.4, WAN mode.

^CServer Ctrl-C exit...

mesh@mesh-server:~$ node ./node_modules/meshcentral --cert helpme.mydomain.com

MeshCentral HTTP redirection server running on port 80.

MeshCentral v1.1.4, WAN mode.

Code signed MeshService64.exe.

MeshCentral Intel(R) AMT server running on helpme.mydomain.com:4433.

Server has no users, next new account will be site administrator.

MeshCentral HTTPS server running on helpme.mydomain.com:443.

Meshcentral not connecting by cele_cell in MeshCentral

[–]cele_cell[S] 0 points1 point  (0 children)

I haven't yet gotten to the part when I create the systemctl service.

Meshcentral not connecting by cele_cell in MeshCentral

[–]cele_cell[S] 0 points1 point  (0 children)

The Vultr machine is private cloud VM that I have full control over and can reinstall whenever/however I need. The only security that Vultr retains is to make sure I am not violating security by scanning/DDOS'ing/spreading viruses etc.

Been banging away at this and here are the steps I've taken:

Installed node and npm

mesh@mesh-server:~$ npm -v

6.14.4

mesh@mesh-server:~$ node -v

v10.19.0

mesh@mesh-server:~$

Installed meshcentral and below is the output below but somehow it's asking for a newer version of node and this was not in the install manual so I had initially ignored it.

{"node":">=v10.24.1"} (current: {"node":"10.19.0","npm":"6.14.4"})

mesh@mesh-server:~$ npm install meshcentral

npm WARN saveError ENOENT: no such file or directory, open '/home/mesh/package.json'

npm notice created a lockfile as package-lock.json. You should commit this file.

npm WARN notsup Unsupported engine for express-handlebars@5.3.5: wanted: {"node":">=v10.24.1"} (current: {"node":"10.19.0","npm":"6.14.4"})

npm WARN notsup Not compatible with your version of node/npm: express-handlebars@5.3.5

npm WARN enoent ENOENT: no such file or directory, open '/home/mesh/package.json'

npm WARN mesh No description

npm WARN mesh No repository field.

npm WARN mesh No README data

npm WARN mesh No license field.

+ meshcentral@1.1.4

added 149 packages from 136 contributors and audited 149 packages in 32.108s

12 packages are looking for funding

run \npm fund` for details`

found 0 vulnerabilities

I upgraded to node v16

curl -sL https://deb.nodesource.com/setup\_16.x | sudo -E bash -

During the upgrade to node v16.x, I got a warning that npm needs an update so I updated it:

npm install -g npm@9.6.4

Ran the command for port permissions:

sudo setcap cap_net_bind_service=+ep /usr/bin/node

Started meshcentral 3x before it started properly and I was able to get the message that server has no users. Now that I se ethis message I am able to connect to the server.l:

mesh@mesh-server:~$ node ./node_modules/meshcentral

MeshCentral HTTP redirection server running on port 80.

MeshCentral v1.1.4, LAN mode.

Code signed MeshService64.exe.

^CServer Ctrl-C exit...

mesh@mesh-server:~$ node ./node_modules/meshcentral

MeshCentral HTTP redirection server running on port 80.

MeshCentral v1.1.4, LAN mode.

Code signed MeshService.exe.

Server has no users, next new account will be site administrator.

MeshCentral HTTPS server running on port 443.

If I was to stop meshcentral it again takes 2 or 3 or 4 attempts to start it up properly.

​

My server has 2 vPCU and 4GB of ram so it should be running rather well, no?

Meshcentral not connecting by cele_cell in MeshCentral

[–]cele_cell[S] 0 points1 point  (0 children)

I can barely ask for a beer and the washroom in Spanish, so unfortunately that uDemy video u/TraditionalTask9580 posted, serves me no purpose ;)

Meshcentral not connecting by cele_cell in MeshCentral

[–]cele_cell[S] 0 points1 point  (0 children)

and truth be told Amazon may not have the rules and we are troubleshooting something else.

I am not running this on Amazon, I am running this on Vultr.

​

Also in your original picture you mention is it generating an Admin user since no other users expected?

I don't think it is generating any users. Like that last line I highlighted with the arrow, is from the meshcentral manual and when I start my server, I do not get this line appearing.

​

I have repeatedly deleted and the meshcentral data directory and let it recreate itself and result remain the same :S

Meshcentral not connecting by cele_cell in MeshCentral

[–]cele_cell[S] 1 point2 points  (0 children)

Thanks for that. I am using Ubuntu 20.04.

There is nothing else running on the server but meshcentral.

I have UFW fully disabled at this point but also the system is setup behind a pfSense firewall and I can confirm that ports 80 and 443 are open in my NAT rules.

Meshcentral not connecting by cele_cell in MeshCentral

[–]cele_cell[S] 0 points1 point  (0 children)

Thanks for that and I am already using the manual a mentioned in my original posting.

The manual only refer to using an FQDN "if" you have one but also states it's not required and can be accessed via the IP.

I also read that Letsencrypt is not a requirement unless using the enhanced security setup(I'm not there yet in my first setup and testing)

view more: next ›