# Can't build LPWAN Server

**URL:** https://forum.lpwanserver.com/t/cant-build-lpwan-server/46
**Category:** Uncategorized
**Created:** [September 15, 2019, 12:56am UTC](https://forum.lpwanserver.com/t/cant-build-lpwan-server/46 "2019-09-15T00:56:20Z")
**Posts on this page:** 1
**Showing post:** 12

<div class="post-metadata">

### Author: ![rhythnic](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.lpwanserver.com/rhythnic/32/12_2.png) [@rhythnic](https://forum.lpwanserver.com/u/rhythnic)
#### Post date: [September 20, 2019, 1:35pm UTC](https://forum.lpwanserver.com/t/cant-build-lpwan-server/46/12 "2019-09-20T13:35:32Z")

</div>

The correct endpoint is [http://prisma:4466/lpwanserver/dev](http://prisma:4466/lpwanserver/dev).

prisma/prisma.yml should read:  
endpoint: ${env:prisma\_url}

This causes causes the generated DB client to attempt to connect to process.env.prisma\_url. You can check if the client was generated correctly by viewing app/generated/prisma-client/index.js. Towards the bottom of the file, you should see process.env.prisma\_url. The development/docker-compose file sets the config file to development/config.json. In that file, the prisma\_url is set to [http://prisma:4466/lpwanserver/dev](http://prisma:4466/lpwanserver/dev). All config variables can be overwritten with environment variables, but in case prisma\_url comes from a config file and not an environment variable, the module app/config/index.js writes the value of config.prisma\_url to process.env.prisma\_url so that it can be used by the DB client.

---

_[View the full topic](https://forum.lpwanserver.com/t/cant-build-lpwan-server/46)._