#tinyproxy — Public Fediverse posts

🚀 Check my latest article on #Tinyproxy a lightweight http(s) proxy server 👇https://carlos.mendible.com/2025/01/18/tinyproxy-a-lightweight-http/https-proxy-server/

@akhil Да, тогда #Tinyproxy не справится, он не поддерживает #кэширование.

@akhil Обязательно #Squid, #Tinyproxy не справится?

Guten Abend zusammen. Ich brauch mal einen Tipp. Ich habe einen #raspberrypi mit #wireguard per #pivpn und #pihole im Heimnetz. Wenn ich mit meinem #smartphone über einen Tunnel mit dem Heimnetz verbunden bin, würde ich gerne für den Zugriff auf #webseiten im #internet die IP Adresse meines #vps nutzen. Auf dem läuft #tinyproxy. Im Raspi ist der Proxy eingetragen und die Prüfung mit curl zeigt auch, dass der Raspi den Proxy nutzt. Nur über den Tunnel verbunden nutzt das Smartphone keinen proxy.

Guten Abend zusammen. Ich brauch mal einen Tipp. Ich habe einen #raspberrypi mit #wireguard per #pivpn und #pihole im Heimnetz. Wenn ich mit meinem #smartphone über einen Tunnel mit dem Heimnetz verbunden bin, würde ich gerne für den Zugriff auf #webseiten im #internet die IP Adresse meines #vps nutzen. Auf dem läuft #tinyproxy. Im Raspi ist der Proxy eingetragen und die Prüfung mit curl zeigt auch, dass der Raspi den Proxy nutzt. Nur über den Tunnel verbunden nutzt das Smartphone keinen proxy.

Critical Tinyproxy Flaw Opens Over 50,000 Hosts to Remote Code Execution – Source:thehackernews.com https://ciso2ciso.com/critical-tinyproxy-flaw-opens-over-50000-hosts-to-remote-code-execution-sourcethehackernews-com/ #rssfeedpostgeneratorecho #CyberSecurityNews #TheHackerNews #Tinyproxy #Critical

I finally found the time to actually check if #DOStodon really works through a SOCKS or HTTP #proxy.
I implemented that feature w/o having a running test proxy instance anywhere.

I just did a minimal configuration of #dante and #tinyproxy and it works! Didn't try authentication, though...

Caddy:
I've been having the worst time with Caddy it seems simple enough but I can't for the life of me get TLS working. I did a bunch of network magic to hop through a series of routers and NATs which is probably part of my problem but I'm seeing packets and the traffic looks ok as far as I can tell. I see that LetsEncrypt issues the certs but then it seems to struggle to serve it back. I was able to point Caddy at other services fine but TLS has been the issue. I need to give it another shot and I will change the approach to securely reach my lab net.

PowerDNS Admin:
I also attempted to spin up PowerDNS Admin. The docker project seems like it has a nice UI but I couldn't get the docker-compose to run successfully. I tried updating a bunch of components and messing with updating the repo but it caused more and more problems rather than solving any. After a couple hours I gave up on it and I think I'll try running a vanilla PowerDNS instance later. I mainly chose it because I also see it in the Proxmox docs as the preferred way to hand over DNS entries from the SDN.

Keycloak:
I got Keycloak running in the lab and the initial client user credential test to work. Then I tried configuring OpenID connect on my CodiMD instance. No go. I couldn't figure out how to align all the parameters on both the Keycloak side and CodiMD side. Then I read the docs and saw the SAML approach may be easier. I followed the example and attempted to map it to the parameters for both to get the IDP working. Still no luck. I've done SAML before and it didn't seem this difficult previously. I think the next attempt will be to try LDAP and sync up my users from GLauth over to Keycloak. If anyone has a good guide or tips on integrating things with Keycloak let me know.

#homelab #selfhosted #proxmox #docker #netbox #ipam #dcim #rancher #vscode #powerdnsadmin #powerdns #codimd #caddy #ghost #tinyproxy #keycloak

Completed a bunch of things in the lab today, including a variety of failures which resulted in earned learning.

Netbox:
I have been wanting to use Netbox as an IPAM/DCIM solution in the lab. The main draw has been so I can organize my network. I was hoping to be able to use the Proxmox SDN IPAM functionality to automatically import VM's, IP's, etc.

I was able to get it spun up in Docker and configured a variety of CI's but after adding it to the SDN configuration I don't see any activity even when including the API. I also verified the API URL and it's working so I don't know if there's something else necessary to start getting new items in Netbox from Proxmox. I looked around in the forums and didn't see anything useful.

For now I am stuck with manual additions until I can figure out why Proxmox can't push updates over. I did see there is a specific plugin called netbox-proxbox but I would have to build that plugin into Netbox and I'm not ready to do that just yet. It looks like that plugin basically requests the data from Proxmox in more of a pull approach.

I'm posting more in the replies below so I don't spam the feeds. Read on if you'd like -->

#homelab #selfhosted #proxmox #docker #netbox #ipam #dcim #rancher #vscode #powerdnsadmin #powerdns #codimd #caddy #ghost #tinyproxy #keycloak

#Tinyproxy is a lightweight yet powerful #opensource HTTP proxy, which can be used as both forward and reverse #HTTP #proxy. In order to properly verify and monitor Tinyproxy, there are a couple of things to look at. 👇
https://www.claudiokuenzler.com/blog/1266/how-to-monitor-verify-tinyproxy-http-forward-proxy