# \[SOLVED\]\[Vaultwarden Dockerless\] Issue setting up

**URL:** <https://vaultwarden.discourse.group/t/solved-vaultwarden-dockerless-issue-setting-up/3572>\
**Category:** Help\
**Created:** [April 22, 2024, 5:20pm UTC](https://vaultwarden.discourse.group/t/solved-vaultwarden-dockerless-issue-setting-up/3572 "2024-04-22T17:20:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ksp](https://avatars.discourse-cdn.com/v4/letter/k/71c47a/32.png) [@ksp](https://vaultwarden.discourse.group/u/ksp)\
**Post date:** [April 22, 2024, 5:20pm UTC](https://vaultwarden.discourse.group/t/solved-vaultwarden-dockerless-issue-setting-up/3572/1 "2024-04-22T17:20:04Z")

</div>

Hello everyone,

I am sorry if that is not appropriate, but I am having an issue in the deployment of Vaultwarden. I have installed the deb from [[https://vaultwarden-deb.pages.dev/](https://vaultwarden-deb.pages.dev/)] (GitHub: [[GitHub - gvtulder/vaultwarden-deb: Debian/Ubuntu repository for Vaultwarden](https://github.com/gvtulder/vaultwarden-deb)]) and I am able to get it running but when I enter IP+port of the Rocket server in my browser, I am faced with a timeout.

Here are the last lines of the log (I have switched it to debug):

```auto
[2024-04-22 19:10:56.976][start][INFO] Rocket has launched from http://127.0.0.1:3000
[2024-04-22 19:11:56.965][vaultwarden::api::core::accounts][DEBUG] Purging auth requests
[2024-04-22 19:11:56.965][vaultwarden::api::core::two_factor][DEBUG] Sending notifications for incomplete 2FA logins
[2024-04-22 19:12:56.967][vaultwarden::api::core::accounts][DEBUG] Purging auth requests
[2024-04-22 19:12:56.967][vaultwarden::api::core::two_factor][DEBUG] Sending notifications for incomplete 2FA logins
[2024-04-22 19:13:56.970][vaultwarden::api::core::accounts][DEBUG] Purging auth requests
[2024-04-22 19:13:56.970][vaultwarden::api::core::two_factor][DEBUG] Sending notifications for incomplete 2FA logins
[2024-04-22 19:14:56.972][vaultwarden::api::core::accounts][DEBUG] Purging auth requests
[2024-04-22 19:14:56.972][vaultwarden::api::core::two_factor][DEBUG] Sending notifications for incomplete 2FA logins
[2024-04-22 19:15:56.974][vaultwarden::api::core::accounts][DEBUG] Purging auth requests
[2024-04-22 19:15:56.974][vaultwarden::api::core::two_factor][DEBUG] Sending notifications for incomplete 2FA logins
[2024-04-22 19:16:56.976][vaultwarden::api::core::accounts][DEBUG] Purging auth requests
[2024-04-22 19:16:56.976][vaultwarden::api::core::two_factor][DEBUG] Sending notifications for incomplete 2FA logins
[2024-04-22 19:17:56.979][vaultwarden::api::core::accounts][DEBUG] Purging auth requests
[2024-04-22 19:17:56.979][vaultwarden::api::core::two_factor][DEBUG] Sending notifications for incomplete 2FA logins
[2024-04-22 19:18:56.981][vaultwarden::api::core::accounts][DEBUG] Purging auth requests
[2024-04-22 19:18:56.981][vaultwarden::api::core::two_factor][DEBUG] Sending notifications for incomplete 2FA logins

```

I can provide any info you need of course.

---

<div class="post-metadata">

**Author:** ![ksp](https://avatars.discourse-cdn.com/v4/letter/k/71c47a/32.png) [@ksp](https://vaultwarden.discourse.group/u/ksp)\
**Post date:** [April 22, 2024, 7:42pm UTC](https://vaultwarden.discourse.group/t/solved-vaultwarden-dockerless-issue-setting-up/3572/2 "2024-04-22T19:42:54Z")

</div>

I’ve solved my problem! The original error was because I moved the data directory but mysql did not like it. I reinstalled the program with the environment conf file, and configured the rocket server address to 0.0.0.0. Finally, I did use certbot to generate ssl certs for my subdomain, but as it was not declared in my nginx conf, there was a return 404; line.