Hi, i’ve been trying today to install the V3 gateway stack, but running into a problem at step 1.
Docker, docker-compose are installed, and i’m using the docker-compose.yml file that is in teh git repo.
Im getting this error. ( debian 9 server )
admin@ip-172-31-30-168:~$ docker-compose pull
ERROR: yaml.scanner.ScannerError: mapping values are not allowed here
in “./docker-compose.yml”, line 529, column 26
So, I’ve bumbled through this… having never used docker before, its a first!
I’ve installed the v3 stack on an Amazon EC2 micro.t2 instance which is running debian version 9. The instructions are mostly good, In the getting started guide, it says to use the provided. docker-compose.yml . I had assumed ( wrongly ) that docker would pull all the files it needs when you use this. that is not the case, you needed to have cloned the github repo first. (doh). Once you’ve done that, then the instructions work as expected.
I’ll submit a pull request with the addition of a single line in the README.md file under prerequisites;
because it was installed in AWS, I did need to consider what network ports are configured for the security groups. The details are usefully in docs/networking.md
While I was able to register a single App, and a device, and point a single gateway to it, Its a bit more ‘raw’ than the public interface ( which is very polished ).
Things i need to work out;
How do you set up the network server so it runs like a service ( like any normal service ) any time it gets rebooted
How to see joins/data etc like you can on the public interface
how to more effectively add/remove devices/apps etc. It seems quite long winded to use the docker-compose commands. I have not figured out how to use the CLI on this.
This is what i did, and the response i got. Since I dont’ have a local browser on the server, i connected to this address using the url https://mypublicip:8885… [ can you modify something so it uses publicly reachable names? ]
I have installed V3 stack on debain 10 server using docker and following official instruction.
With my installation I was able to authenticate user using http://10.0.0.100:1885/ (not locally on server) successfully (I saw response 200 on docker log) but I didn’t gain access to console because I was redirected on http://localhost:1885/console (so on the server).
If I try with browser locally on the server login in was successfully.
I haven’t configure at moment any TLS.
Anyone could support me please understanding why server is redirecting locally response and not using ip address?
this was my first attempt. However, if I use the username and password defined in ttn-lw-stack.yml File I’m still not able to login.
Following the guide that I mentioned before https://thethingsstack.io/v3.6.0/guides/getting-started/ I didn’t really create a admin account. They are mentioning at some point that I can register an account (if needed) but this doesn’t seem to work properly. Because when I try to register a new user nothing is happening. Even in the log file no entry is produced.
Since I still had some issue when I was running tttn stack I tried to reinstall the server as described in the previous mentioned documentation. I even used the configuration file as described in the documentation. Unfortunately, I keep getting following error message when running:
docker-compose run --rm stack is-db init
Error Message: Starting ttn_cockroach_1 ... done Starting ttn_redis_1 ... done INFO Connecting to Identity Server database... dial tcp: lookup cockroach on 127.0.0.11:53: no such host
Below the content of my docker-compose.yml file:
I found I had to put it in the ./config/stack folder that is created when you run the docker-compose up command. I think the volumes part of the .yml file mounts ./config/stack as /config inside the container. Not well documented at all…