# Reverse Proxy with Raspberry Pi

**URL:** <https://community.letsencrypt.org/t/reverse-proxy-with-raspberry-pi/179104>\
**Category:** Help\
**Created:** [June 8, 2022, 6:40am UTC](https://community.letsencrypt.org/t/reverse-proxy-with-raspberry-pi/179104 "2022-06-08T06:40:10Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Toastyv](https://avatars.discourse-cdn.com/v4/letter/t/aeb1de/32.png) [@Toastyv](https://community.letsencrypt.org/u/Toastyv)\
**Post date:** [June 8, 2022, 6:40am UTC](https://community.letsencrypt.org/t/reverse-proxy-with-raspberry-pi/179104/1 "2022-06-08T06:40:10Z")

</div>

Hi everyone,

I'm hoping someone can help me regarding my situation. I have a raspberry pi with airsonic that I'd like to stream my music remotely with a reverse proxy.

Following the documentation on Airsonic's website, it mentions to have the certificates installed from Let's Encrypt/Certbot. Because I'd like to have this accessed only by myself, I'm lost since I don't have a domain name.

My domain is: Not available

I ran this command: sudo certbot certonly --standalone

It produced this output: The Let's Encrypt certificate authority will not issue certificates for a bare IP address.

My web server is (include version): Not available

The operating system my web server runs on is (include version): Debian 11 Bullseye

My hosting provider, if applicable, is: Not available

I can login to a root shell on my machine (yes or no, or I don't know): I don't know

Am very new to all this so sorry in advanced if I don't know what you might be explaining.

What is the best way to approach this? Any help will be greatly appreciated!

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [June 8, 2022, 6:43am UTC](https://community.letsencrypt.org/t/reverse-proxy-with-raspberry-pi/179104/2 "2022-06-08T06:43:24Z")

</div>

Hi @Toastyv, and welcome to the LE community forum 🙂

LE certs require a globally registered domain name.  
That said, if you have Internet access, you can obtain an FQDN from a free domain.  
And then use that to validate and obtain a cert via HTTP authentication (or use DNS authentication if your ISP blocks HTTP [TCP port 80]).  
OR  
You might be able to run the music without a certificate  
OR  
You might be able to create a self-signed cert

---

<div class="post-metadata">

**Author:** ![Toastyv](https://avatars.discourse-cdn.com/v4/letter/t/aeb1de/32.png) [@Toastyv](https://community.letsencrypt.org/u/Toastyv)\
**Post date:** [June 8, 2022, 6:47am UTC](https://community.letsencrypt.org/t/reverse-proxy-with-raspberry-pi/179104/3 "2022-06-08T06:47:30Z")

</div>

Hi Rg305,

Thanks and really appreciate the speedy response!

Can you please point me in the right direction about creating self signed certificates? Do I enter this once it prompts me for a domain name? Thanks again!

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [June 8, 2022, 6:49am UTC](https://community.letsencrypt.org/t/reverse-proxy-with-raspberry-pi/179104/4 "2022-06-08T06:49:08Z")

</div>

I can't see the menu/screen prompt you are looking at.  
And I really don't have the time right now - it's 2:48 am and I'm heading to bed 💤

---

<div class="post-metadata">

**Author:** ![Toastyv](https://avatars.discourse-cdn.com/v4/letter/t/aeb1de/32.png) [@Toastyv](https://community.letsencrypt.org/u/Toastyv)\
**Post date:** [June 8, 2022, 6:50am UTC](https://community.letsencrypt.org/t/reverse-proxy-with-raspberry-pi/179104/5 "2022-06-08T06:50:55Z")

</div>

No problem, thanks for contributing! It's a good start at least.

---

<div class="post-metadata">

**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\
**Post date:** [June 8, 2022, 7:14am UTC](https://community.letsencrypt.org/t/reverse-proxy-with-raspberry-pi/179104/6 "2022-06-08T07:14:43Z")

</div>

> [@Toastyv](#):
>
> Can you please point me in the right direction about creating self signed certificates?

have fun:

> [@After del. certificate, IP out of reach](https://community.letsencrypt.org/t/after-del-certificate-ip-out-of-reach/174117/11):
>
> …

---

<div class="post-metadata">

**Author:** ![Toastyv](https://avatars.discourse-cdn.com/v4/letter/t/aeb1de/32.png) [@Toastyv](https://community.letsencrypt.org/u/Toastyv)\
**Post date:** [June 8, 2022, 10:39am UTC](https://community.letsencrypt.org/t/reverse-proxy-with-raspberry-pi/179104/7 "2022-06-08T10:39:25Z")

</div>

Thanks 9peppe; do I have to input this code when it prompts for a domain? Again sorry if this is all common knowledge.

---

<div class="post-metadata">

**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\
**Post date:** [June 8, 2022, 11:24am UTC](https://community.letsencrypt.org/t/reverse-proxy-with-raspberry-pi/179104/8 "2022-06-08T11:24:04Z")

</div>

No, you either use Certbot and get a Let's Encrypt certificate,

OR you use that code to get a self signed certificate.

---

<div class="post-metadata">

**Author:** ![Toastyv](https://avatars.discourse-cdn.com/v4/letter/t/aeb1de/32.png) [@Toastyv](https://community.letsencrypt.org/u/Toastyv)\
**Post date:** [June 9, 2022, 12:34am UTC](https://community.letsencrypt.org/t/reverse-proxy-with-raspberry-pi/179104/9 "2022-06-09T00:34:04Z")

</div>

Ok thanks 9peppe, will give it a go.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [July 9, 2022, 12:35am UTC](https://community.letsencrypt.org/t/reverse-proxy-with-raspberry-pi/179104/10 "2022-07-09T00:35:01Z")

</div>

Closed on July 9, 2022, 12:35am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
