# Discourse version not found, likely because I rate limited myself
**URL:** https://meta.discourse.org/t/discourse-version-not-found-likely-because-i-rate-limited-myself/355246
**Category:** Self-hosting
**Created:** [March 1, 2025, 10:46pm UTC](https://meta.discourse.org/t/discourse-version-not-found-likely-because-i-rate-limited-myself/355246 "2025-03-01T22:46:58Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Mako-Poisoned](https://meta.discourse.org/u/Mako-Poisoned)
#### Post date: [March 1, 2025, 10:46pm UTC](https://meta.discourse.org/t/discourse-version-not-found-likely-because-i-rate-limited-myself/355246/1 "2025-03-01T22:46:58Z")
Hi there,
Over the last few days, I had reinstalled discourse with no issue. However, upon final install (on the same subdomain), I noticed that I could not connect to the site after installation.
I am using cloudflare for DNS, have the approriate A record pointing to my server IP, grey cloud (just DNS).
When running `./discourse-doctor`, I would notice that it would say `DISCOURSE VERSION NOT FOUND`
Here is the output, if you’d like to see:
```plaintext
DOCKER VERSION: Docker version 26.1.3, build 26.1.3-0ubuntu1.1
DOCKER PROCESSES (docker ps -a)
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
78b5cb0b62ba local_discourse/app "/sbin/boot" 46 minutes ago Up 45 minutes 0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp app
78b5cb0b62ba local_discourse/app "/sbin/boot" 46 minutes ago Up 45 minutes 0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp app
Discourse container app is running
==================== PLUGINS ====================
- git clone https://github.com/discourse/docker_manager.git
No non-official plugins detected.
See https://github.com/discourse/discourse/blob/main/lib/plugin/metadata.rb for the official list.
========================================
Discourse version at discourse.kwehchocobo.com: NOT FOUND
Discourse version at localhost: NOT FOUND
==================== MEMORY INFORMATION ====================
RAM (MB): 2062
total used free shared buff/cache available
Mem: 1967 1425 110 27 649 542
Swap: 2047 87 1960
==================== DISK SPACE CHECK ====================
---------- OS Disk Space ----------
Filesystem Size Used Avail Use% Mounted on
/dev/vda1 58G 11G 47G 19% /
==================== DISK INFORMATION ====================
Disk /dev/vda: 60 GiB, 64424509440 bytes, 125829120 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: DE1E7A6C-B4DD-46F7-BA1E-2411007BBB6F
Device Start End Sectors Size Type
/dev/vda1 2324480 125829086 123504607 58.9G Linux filesystem
/dev/vda13 2048 2097152 2095105 1023M Linux extended boot
/dev/vda14 2099200 2107391 8192 4M BIOS boot
/dev/vda15 2107392 2324479 217088 106M EFI System
Partition table entries are not in disk order.
Disk /dev/vdb: 482 KiB, 493568 bytes, 964 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
==================== END DISK INFORMATION ====================
```
I assume that Discourse cannot be found because of the lack of SSL certification (I am following the proper discourse installation method as seen [here](https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md).
When I attempt: `sudo certbot certonly --standalone -d discourse.kwehchocobo.com`
**Note: regarding the next input…**
**I believe this would explain why I can no longer connect to the domain upon my final installation attempt. I also believe this is why discourse doctor is telling me that it cannot find discourse at the domain.**
Also, **how long am I rate limited? I am in the pacific timezone. I believe it would be 4:13 PM PST? Does that mean I can attempt to reinstall discourse with SSL from the installer after that time and not run into rate limiting?**
Anyways, here is my output:
````Saving
Requesting a certificate for discourse.kwehchocobo.com
An unexpected error occurred:
too many certificates (5) already issued for this exact set of domains in the last 168h0m0s, retry after 2025-03-02 23:45:07 UTC: see https://letsencrypt.org/docs/rate-limits/#new-certificates-per-exact-set-of-hostnames
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
root@chocobo-kweh:/etc/letsencrypt# ```
````
---
### Author:  [@Arkshine](https://meta.discourse.org/u/Arkshine)
#### Post date: [March 1, 2025, 11:56pm UTC](https://meta.discourse.org/t/discourse-version-not-found-likely-because-i-rate-limited-myself/355246/2 "2025-03-01T23:56:58Z")
Hey, welcome!
I think you do have the answer in your quote:
> [@Mako-Poisoned](#):
>
> Also, **how long am I rate limited?**
> [@Mako-Poisoned](#):
>
> `retry after 2025-03-02 23:45:07 UTC`
It seems you’re allowed to retry after ~24h.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [April 1, 2025, 12:17am UTC](https://meta.discourse.org/t/discourse-version-not-found-likely-because-i-rate-limited-myself/355246/4 "2025-04-01T00:17:40Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.