# Another domain doesn't work, and installation ended
**URL:** https://meta.discourse.org/t/another-domain-doesnt-work-and-installation-ended/329451
**Category:** Self-hosting
**Created:** [October 5, 2024, 8:48am UTC](https://meta.discourse.org/t/another-domain-doesnt-work-and-installation-ended/329451 "2024-10-05T08:48:23Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [October 5, 2024, 8:48am UTC](https://meta.discourse.org/t/another-domain-doesnt-work-and-installation-ended/329451/1 "2024-10-05T08:48:23Z")
Continuing the discussion from [Installation ended, what do I do now?](https://meta.discourse.org/t/installation-ended-what-do-i-do-now/321463):
So I’ve tried again with [ndforum.mooo.com](http://ndforum.mooo.com). @David_Ghost crt.sh says no certs found, yet I have added my IP as the value of an A record.
I have tried searching it through [iplocation.io](http://iplocation.io), which says N/A for all fields, but notes that it is on a LAN. Is this the reason?
From the console:
```plaintext
I, [2024-10-05T08:29:35.284170 #1] INFO -- : Replacing location @discourse { with location @discourse {
add_header Strict-Transport-Security 'max-age=31536000'; # remember the certificate for a year and automatically connect to HTTPS for this domain in /etc/nginx/conf.d/discourse.conf
I, [2024-10-05T08:29:35.285258 #1] INFO -- : > echo "Beginning of custom commands"
I, [2024-10-05T08:29:35.290139 #1] INFO -- : Beginning of custom commands
I, [2024-10-05T08:29:35.290880 #1] INFO -- : > echo "End of custom commands"
I, [2024-10-05T08:29:35.296122 #1] INFO -- : End of custom commands
I, [2024-10-05T08:29:35.296743 #1] INFO -- : Terminating async processes
I, [2024-10-05T08:29:35.296924 #1] INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main pid: 36
2024-10-05 08:29:35.297 UTC [36] LOG: received fast shutdown request
I, [2024-10-05T08:29:35.297792 #1] INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 104
104:signal-handler (1728116975) Received SIGTERM scheduling shutdown...
2024-10-05 08:29:35.320 UTC [36] LOG: aborting any active transactions
104:M 05 Oct 2024 08:29:35.332 # User requested shutdown...
104:M 05 Oct 2024 08:29:35.333 * Saving the final RDB snapshot before exiting.
2024-10-05 08:29:35.339 UTC [36] LOG: background worker "logical replication launcher" (PID 51) exited with exit code 1
2024-10-05 08:29:35.339 UTC [46] LOG: shutting down
104:M 05 Oct 2024 08:29:35.383 * DB saved on disk
104:M 05 Oct 2024 08:29:35.383 # Redis is now ready to exit, bye bye...
2024-10-05 08:29:35.792 UTC [36] LOG: database system is shut down
sha256:dda45b5fe470c9062432fc15263c58cc33e64a8835a26e7918238f831dce38ca
fca73e2e52e0f4620e8d3ccedc71166815cb2c23566da591acbc92cb81e772c1
Removing old container
+ /usr/bin/docker rm app
app
+ /usr/bin/docker run --shm-size=512m -d --restart=always -e LANG=en_US.UTF-8 -e RAILS_ENV=production -e UNICORN_WORKERS=8 -e UNICORN_SIDEKIQS=1 -e RUBY_GC_HEAP_GROWTH_MAX_SLOTS=40000 -e RUBY_GC_HEAP_INIT_SLOTS=400000 -e RUBY_GC_HEAP_OLDOBJECT_LIMIT_FACTOR=1.5 -e DISCOURSE_DB_SOCKET=/var/run/postgresql -e DISCOURSE_DB_HOST= -e DISCOURSE_DB_PORT= -e LETSENCRYPT_DIR=/shared/letsencrypt -e DISCOURSE_FORCE_HTTPS=true -e LC_ALL=en_US.UTF-8 -e LANGUAGE=en_US.UTF-8 -e DISCOURSE_HOSTNAME=ndforum.mooo.com -e DISCOURSE_DEVELOPER_EMAILS=[CENSORED] -e DISCOURSE_SMTP_ADDRESS=smtp.gmail.com -e DISCOURSE_SMTP_PORT=587 -e DISCOURSE_SMTP_USER_NAME=[CENSORED] -e DISCOURSE_SMTP_PASSWORD=[CENSORED] -e DISCOURSE_SMTP_DOMAIN=gmail.com -e DISCOURSE_NOTIFICATION_EMAIL=[CENSORED] -e LETSENCRYPT_ACCOUNT_EMAIL=me@example.com -h raspberrypi-app -e DOCKER_HOST_IP=[CENSORED] --name app -t -p 80:80 -p 443:443 -v /var/discourse/shared/standalone:/shared -v /var/discourse/shared/standalone/log/var-log:/var/log --mac-address 02:ee:d2:40:e1:0e local_discourse/app /sbin/boot
561ebf80d13c8c8e2d97f2a26a0cd13f61a8b8b9400347ca54b90d3a231d13b4
```
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [October 5, 2024, 8:57am UTC](https://meta.discourse.org/t/another-domain-doesnt-work-and-installation-ended/329451/2 "2024-10-05T08:57:28Z")
> [@NateDhaliwal](#):
>
> [ndforum.mooo.com](http://ndforum.mooo.com)
I cannot even ping this server, but an A record is clearly picked up.
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [October 5, 2024, 9:04am UTC](https://meta.discourse.org/t/another-domain-doesnt-work-and-installation-ended/329451/3 "2024-10-05T09:04:41Z")
Odd. I definitely made an A record, but I have no idea why it cannot be pinged…
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [October 5, 2024, 9:05am UTC](https://meta.discourse.org/t/another-domain-doesnt-work-and-installation-ended/329451/4 "2024-10-05T09:05:39Z")
Where is your server?
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [October 5, 2024, 9:06am UTC](https://meta.discourse.org/t/another-domain-doesnt-work-and-installation-ended/329451/5 "2024-10-05T09:06:52Z")
On my Pi. Should I setup a Cloudflare Tunnel?
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [October 5, 2024, 9:08am UTC](https://meta.discourse.org/t/another-domain-doesnt-work-and-installation-ended/329451/6 "2024-10-05T09:08:55Z")
Yes, that’s probably a good idea as your ISP may not allow traffic otherwise?
> [@Install Discourse on a residential internet with Cloudflare Tunnel](https://meta.discourse.org/t/discourse-in-a-residential-internet-with-cloudflare-tunnel/211297?ref=blog.discourse.org):
>
> Since [Discourse now has support for running on a Raspberry Pi](https://blog.discourse.org/2021/12/2021-12-07-discourse-on-a-raspberry-pi/), running a small instance in your home lab will become a common use case. However, many residential ISPs block incoming traffic to the ports 80/443 that Discourse need. For our demo site at [https://discourse-on-a-pi.falco.dev/](https://discourse-on-a-pi.falco.dev/) we used [Cloudflare Tunnel](https://blog.cloudflare.com/tunnel-for-everyone/) to work around this, and you can do it too! Setup your tunnel First, follow the following guide: The only change you need is changing the URL from url: http://localhost:8000 to url…
But I don’t think this is the whole story.
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [October 5, 2024, 9:45am UTC](https://meta.discourse.org/t/another-domain-doesnt-work-and-installation-ended/329451/7 "2024-10-05T09:45:50Z")
Also - have you set up port forwarding on your router?
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [October 6, 2024, 3:42am UTC](https://meta.discourse.org/t/another-domain-doesnt-work-and-installation-ended/329451/8 "2024-10-06T03:42:53Z")
No, I have not.
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [October 6, 2024, 10:11am UTC](https://meta.discourse.org/t/another-domain-doesnt-work-and-installation-ended/329451/9 "2024-10-06T10:11:02Z")
@merefield Is it necessary to? Or will the tunnel suffice?
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [October 6, 2024, 10:30am UTC](https://meta.discourse.org/t/another-domain-doesnt-work-and-installation-ended/329451/10 "2024-10-06T10:30:39Z")
Given the guide does not mention it, I would go with tunnel only.
I’m just used to the idea that when there is a server on a home network, you need to route the traffic somehow. Perhaps the Cloudfare set up and choice of port sorts that out automatically somehow. (anyone feel free to chime in here!)