Hi @wint0178, when you logged in to the server, if you see this error, it was happened before login.
If it comes only one time and all other functions are working as expected, please ignore this error.
Posts made by jkandasa
-
RE: Request failed with status code 401
-
RE: Request failed with status code 401
@wint0178 can you access the server on the localhost or in LAN?
Are you seeing the error on UI? Can you share the screen shot? -
RE: Trouble with MC v2 install on RPi 4
Thanks @wint0178 !!
I will go through the installation documentation and sync with your update. -
RE: Trouble with MC v2 install on RPi 4
@wint0178 Thanks for the details
I see you have an trailing space after\
("--env TZ="Asia/Kolkata" \ "
), that leadsrestart
command not found
I have updated your timezone and removed the extra space, can you please try the following command to start the MyController server?go to your mycontroller directory(root of
mc_home
and location ofmycontroller.yaml
) and run the following commanddocker run --detach --name mycontroller \ --network mycontroller \ --publish 8080:8080 \ --publish 8443:8443 \ --publish 9443:9443 \ --volume $PWD/mc_home:/mc_home \ --volume $PWD/mycontroller.yaml:/app/mycontroller.yaml \ --env TZ="America/Chicago" \ --restart unless-stopped \ docker.io/mycontroller/server:2.0.0
If it doesn't comes up please run the following command, I just removed the
--detach
(don't run on background) and added--rm
(remove the container on termination)docker run --rm --name mycontroller \ --network mycontroller \ --publish 8080:8080 \ --publish 8443:8443 \ --publish 9443:9443 \ --volume $PWD/mc_home:/mc_home \ --volume $PWD/mycontroller.yaml:/app/mycontroller.yaml \ --env TZ="America/Chicago" \ --restart unless-stopped \ docker.io/mycontroller/server:2.0.0
I assume if I uninstall docker to try and update it using the code you include in the documentation, as you suggested, that I will also need to reinstall influxdb, natsio, and mqtt. Is that correct?
Yes, In the docker just removes the containers and creates from fresh.
I was just messing with your install from executable binary instructions and I got the MC server running and can pull it up at localhost:8080. When I run docker ps -a I am still getting the same three services running: mqtt, influxdb, and natsio. Is this correct?
executable is different than the docker. It will not be come under
docker ps
command.
It executes directly on the host system.
I would recommend to use docker version of mycontroller, for the portability and maintainabilitythe running server on localhost has a warning that the Metrics database is disabled. I assume this has to do with installing MC from the binary, but it feels like progress anyway.
This is because, executable which is running on outside of docker network and can not resolve the hostname used inside docker. If you replace hostname of
mc_natsio
,mc_influxdb
tolocalhost
on yourmycontroller.yaml
[1] should work. However, I would recommend to try the docker version of mycontroller.[1] - If you apply this change, it will not work on docker version of mycontroller
-
RE: Trouble with MC v2 install on RPi 4
@wint0178 What is the log do you see on the
mycontroller
container?docker logs mycontroller
and what is the output of,
docker ps -a
This is where I get hung up, but I'm not sure if I have settings above here incorrect or if there is something wrong with the following install/run commands.
Can you please elaborate? Does the terminal hung to return?
-
RE: Setting up MQTT
@wint0178 on the other post, I see you were able to see the nodes. Still do you see this issue?
-
RE: Setting up MQTT
@wint0178 Are you using MySensors library?
Your MQTT broker should be accessible to all of your hardware gateway nodes and MyController server. MyController server is acting as MQTT client, just like another MQTT device in your network. -
RE: SSD filled overnight
@wint0178 You can use letsencrypt certification setup with
https_acme
to your DDNS setup, https://v2.mycontroller.org/docs/installation/advanced-installation/backend-configuration/ -
RE: Moving Server to another location
@jkandasa I have fixed this. available in the docker container(
2.1.0-devel
). yet to update in executable. -
RE: SSD filled overnight
@wint0178 I have not experienced this kind of issue. check the filesystem. you can find the root cause. Please let us know your findings. You can check this after your family road trip
-
RE: Gateway setup for MCv2 using MySensors
@wint0178 No, keep default labels. as @JeeLet mentioned can you check any other service is consuming the serial port? Do you see any error on the gateway?
-
RE: Moving Server to another location
@JeeLet @wint0178 Yes, this known issue. but it will not impact the functionality. I will fix this soon.
-
RE: Remote access to MCv2 Dashboard
@wint0178 we have many options, one of them is, port forward required services as you mentioned in your router. you need separate entry for each service(MyController, MQTT broker, etc.,)
Some use reverse proxy. do one a port forward to your reverse proxy via 443 and 80, then do all other changes in your reverse proxy. Someof the famous reverse proxy servers are caddyserver, traefik, nginx, etc.,
-
RE: Moving Server to another location
@wint0178 said in Moving Server to another location:
As for the dashboard, there is nothing there. In v1.5 there was a clock and location, but not in v2.0. Is here a way to add those back?
No, for now in V2 we do not have clock and location.
-
RE: Gateway setup for MCv2 using MySensors
@wint0178 what is the labels do you use in
mycontroller.yaml
undergateway
? you have to use that label in your gateway settings label section. -
RE: Moving Server to another location
Once I started MC on my Pi the dashboard comes up, but I get the following message (or error) in the upper right corner:
Request failed with status code 401
URL: /api/datarepositoryDo you have anything in the dashboard referring data repository and it is not there in data repository?
Message: {"success":false,"message":"401 Unauthorized","data":null}
I think you existing login session and restarted the MyContorller, so leads this error and redirect to login page. but after login still it shows the previous error. I will try to remove that.
-
RE: Moving Server to another location
@wint0178 I would recommend to use
docker network
create a docker network in your rpi,docker network create mycontroller
and include the
--network=mycontroller
in all of your services, like mycontroller, influxdb, natsio, mqtt server, etc.,
and use name of the service in the place of IPs inmycontroller.yaml
Few sample:
docker run --detach --name mc_natsio \ --network mycontroller \ --publish 4222:4222 \ --env TZ="Asia/Kolkata" \ --restart unless-stopped \ nats:2.2.2-alpine
docker run --detach --name mycontroller \ --network mycontroller \ --publish 8080:8080 \ --publish 8443:8443 \ --publish 9443:9443 \ --volume $PWD/mc_home:/mc_home \ --volume $PWD/mycontroller.yaml:/app/mycontroller.yaml \ --env TZ="Asia/Kolkata" \ --restart unless-stopped \ docker.io/mycontroller/server:2.0.0
...omitted... bus: ...omitted... server_url: nats://mc_natsio:4222 metric: ...omitted... uri: http://influxdb:8086
-
RE: Docker Install Error
@wint0178 At the time of writing the document in RPI the default installation does not have docker 20.x or above. Hence I proposed this method. In your installation if you have latest version of docker, you can install with
apt install...
command. I think I took the steps from https://github.com/docker/docker-install -
RE: Armbian - MyC V2 - install
@JeeLet @wint0178 recently I released the version 2.0.0, the location changes. also I changed some of the paths. I will go through the installation steps soon as possible and update the required corrections
-
RE: Is NATS.io needed on RPi?
hi @wint0178,
MQTT Broker
- if you plan to connect your gateway via MQTT, you need an mqtt broker. If you already one. you can use that. You can have MQTT broker in any system, that should be accessible for MyController and your gateway device. If you do not have complex system, you can keep everything on the same system.MongoDB
- for storage the default option is in-memory database. It keeps all the configurations(except metrics) in memory and dumps to dis in an interval. It will be faster. You can take a frequent backup with schedule. But someone wants to keep the storage in mongoDB, may be due to large setof configurations or to keep the data in remote location, or other reasons. It is up to you. fyi, I am using in-memory db and I do not see an issue till now(about 2 years)InfludDB
- you need to have this database, if you want graphs and metrics details
I hope I have addressed your queries