# Cannot access topics after upgrade from 1.6.0.beta1 to beta2

**URL:** <https://meta.discourse.org/t/cannot-access-topics-after-upgrade-from-1-6-0-beta1-to-beta2/42992>\
**Category:** Product Support\
**Created:** [22 Abril , 2016 15:15 UTC](https://meta.discourse.org/t/cannot-access-topics-after-upgrade-from-1-6-0-beta1-to-beta2/42992 "2016-04-22T15:15:40Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![chrisc](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chrisc/32/119982_2.png) [@chrisc](https://meta.discourse.org/u/chrisc)\
**Post date:** [31 Dezembro , 2017 10:54 UTC](https://meta.discourse.org/t/cannot-access-topics-after-upgrade-from-1-6-0-beta1-to-beta2/42992/16 "2017-12-31T10:54:07Z")

</div>

> Is there a `tail -f` version of `./launcher logs app` ?

You can get the running container ID with `docker ps` and then use `docker logs -f` so putting them together (for a server running one container as you typically have with Discourse):

```plaintext
docker logs -f $(docker ps -q)

```

You might want to run this in `screen`.

---

_[View the full topic](https://meta.discourse.org/t/cannot-access-topics-after-upgrade-from-1-6-0-beta1-to-beta2/42992)._