# Using atlas-run with later versions of Confluence

**URL:** <https://community.developer.atlassian.com/t/using-atlas-run-with-later-versions-of-confluence/13269>\
**Category:** Confluence Server\
**Tags:** developer-experience\
**Created:** [January 9, 2018, 9:36am UTC](https://community.developer.atlassian.com/t/using-atlas-run-with-later-versions-of-confluence/13269 "2018-01-09T09:36:53Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![martin](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/martin/32/35758_2.png) [@martin](https://community.developer.atlassian.com/u/martin)\
**Post date:** [January 9, 2018, 9:36am UTC](https://community.developer.atlassian.com/t/using-atlas-run-with-later-versions-of-confluence/13269/1 "2018-01-09T09:36:53Z")

</div>

I’m trying to start a dev server for one of our addons using one of the later Confluence versions. I have been experimenting back and forth, but whenever I go over version 6.3 it seems to be running into problems.

There are many mentions of JDBC and databases in the logs. Has something changed with how the memory database is used for dev servers?

---

<div class="post-metadata">

**Author:** ![martin](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/martin/32/35758_2.png) [@martin](https://community.developer.atlassian.com/u/martin)\
**Post date:** [January 9, 2018, 10:20am UTC](https://community.developer.atlassian.com/t/using-atlas-run-with-later-versions-of-confluence/13269/2 "2018-01-09T10:20:04Z")

</div>

Google found this one for me:

[https://confluence.atlassian.com/confkb/upgrade-to-confluence-6-or-above-fails-when-using-the-embedded-database-917963158.html](https://confluence.atlassian.com/confkb/upgrade-to-confluence-6-or-above-fails-when-using-the-embedded-database-917963158.html)

Tried the workaround, the server now starts. However nothing is served when visiting localhost:1990. Do I need to change anything to make it work with the new embedded database?

---

<div class="post-metadata">

**Author:** ![ianRagudo](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/ianragudo/32/44527_2.png) [@ianRagudo](https://community.developer.atlassian.com/u/ianRagudo)\
**Post date:** [January 10, 2018, 3:46am UTC](https://community.developer.atlassian.com/t/using-atlas-run-with-later-versions-of-confluence/13269/3 "2018-01-10T03:46:04Z")

</div>

Hi, @martin.

Without changing any configuration on my machine, it defaults to [http://computerName:1990/confluence](http://computerName:1990/confluence); without the **/confluence** , the page will not be found. If you want to make sure that localhost will be used, pass `--server localhost` i.e. `atlas-run --server localhost`.

Cheers,  
Ian

---

<div class="post-metadata">

**Author:** ![martin](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/martin/32/35758_2.png) [@martin](https://community.developer.atlassian.com/u/martin)\
**Post date:** [January 10, 2018, 1:08pm UTC](https://community.developer.atlassian.com/t/using-atlas-run-with-later-versions-of-confluence/13269/4 "2018-01-10T13:08:31Z")

</div>

Thanks for your reply @ianRagudo! Unfortunately it did not work for me. Still getting 404:s from the server on [http://localhost:1990/confluence](http://localhost:1990/confluence).

Do I need to specify another database driver for my addon when moving to developing for Confluence 6.x to get it to play nicely with the embedded database?

---

<div class="post-metadata">

**Author:** ![martin](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/martin/32/35758_2.png) [@martin](https://community.developer.atlassian.com/u/martin)\
**Post date:** [January 12, 2018, 10:15am UTC](https://community.developer.atlassian.com/t/using-atlas-run-with-later-versions-of-confluence/13269/5 "2018-01-12T10:15:00Z")

</div>

It seems like I have managed to solve our server startup problems.

Reconditioning the POM with Java 1.8, AMPS 6.3.6 and AO 1.2.0 seems to have done the trick. The server now starts and serves on localhost as expected.

Thanks!