# Own hosted openrouteservice instance not working
**URL:** https://ask.openrouteservice.org/t/own-hosted-openrouteservice-instance-not-working/1800
**Category:** openrouteservice
**Created:** [June 9, 2020, 9:22pm UTC](https://ask.openrouteservice.org/t/own-hosted-openrouteservice-instance-not-working/1800 "2020-06-09T21:22:43Z")
**Posts on this page:** 1
**Showing post:** 9
### Author:  [@nils](https://ask.openrouteservice.org/u/nils)
#### Post date: [June 14, 2020, 8:33am UTC](https://ask.openrouteservice.org/t/own-hosted-openrouteservice-instance-not-working/1800/9 "2020-06-14T08:33:20Z")
@LittleBoxOfChicken @SimonDahrs
If you could assist a little by trying if this PR resolves your issues, that’d be appreciated:
>
>
> \### Pull Request Checklist
>
> \- \[x\] 1. I have \[\*\*rebased\*\*\](https://github.com/G…IScience/openrouteservice/blob/master/CONTRIBUTE.md#pull-request-guidelines) the latest version of the master branch into my feature branch and all conflicts have been resolved.
> \- \[x\] 2. I have added information about the change/addition to functionality to the CHANGELOG.md file under the \[Unreleased\] heading.
> \- \[\] 3. I have documented my code using JDocs tags.
> \- \[\] 4. I have removed unnecessary commented out code, imports and System.out.println statements.
> \- \[\] 5. I have written JUnit tests for any new methods/classes and ensured that they pass.
> \- \[\] 6. I have created API tests for any new functionality exposed to the API.
> \- \[\] 7. If changes/additions are made to the app.config file, I have added these to the app.config wiki page on github along with a short description of what it is for, and documented this in the Pull Request (below).
> \- \[\] 8. I have built graphs with my code of the Heidelberg.osm.gz file and run the api-tests with all test passing
> \- \[x\] 9. I have referenced the Issue Number in the Pull Request (if the changes were from an issue).
> \- \[\] 10. For new features or changes involving building of graphs, I have tested on a larger dataset (at least Germany) and the graphs build without problems (i.e. no out-of-memory errors).
> \- \[\] 11. For new features or changes involving the graphbuilding process (i.e. changing encoders, updating the importer etc.), I have generated longer distance routes for the affected profiles with different options (avoid features, max weight etc.) and compared these with the routes of the same parameters and start/end points generated from the current live ORS. If there are differences then the reasoning for these \*\*MUST\*\* be documented in the pull request.
> \- \[x\] 12. I have written in the Pull Request information about the changes made including their intended usage and why the change was needed.
>
> Fixes #742 .
>
> \### Information about the changes
> \- Key functionality added:
> - default \`app.config.sample\` from \`./openrouteservice/src/main/resources/app.config.sample\` is used to build the image
> - be aware the image changes the \`app.config\` to
> - only build \`car\` instead of all profiles
> - \`init\_threads: 1\` since \> 1 can cause issues
> - changes all paths to docker image paths
> - uses the default \`heidelberg.osm.gz\`
> \- Reason for change: Before we had two \`app.config\`, one for the native Java app, one for docker. This PR removes that maintenance burden.
The image is not available on dockerhub yet, but you can pull the associated branch and do a manual build:
```bash
docker build -t openrouteservice/openrouteservice:test_docker --build-arg OSM_FILE=./your_osm.pbf APP_CONFIG=./your.app.config .
```
Or even omit the `build-arg`s and specify those as environment variables in the `docker-compose.yml` to launch a container.
---
_[View the full topic](https://ask.openrouteservice.org/t/own-hosted-openrouteservice-instance-not-working/1800)._