From the Windows side (assuming you’re using Windows to connect, considering it’s RDP and not VNC), you can open PowerShell and test to see if the Raspberry Pi is even listening for RDP connections with:

Test-NetConnection x.x.x.x -port 3389

Replace x.x.x.x with the IP address of the Raspberry Pi. If it shows successful, then the Raspberry Pi is listening for RDP connections.

Do you know what RDP package you installed, and what operating system you’re running (Bookworm, Bullseye, etc)? I don’t have a raspberry pi with a desktop to test on, but if you’re using xrdp you could try:

sudo systemctl status xrdp

Does this give any input? If not, then you’ll need to know what package you installed to get RDP, assuming one is still installed even. If it does give you a message it might be a hint as to why it’s not working.

If you get output from the above command you can also try:

sudo journalctl -b | grep -C 2 xrdp

There are much better ways of searching journalctl but I’m a noob too. The -b returns only errors from the last boot time, the -C returns that many lines before and after a match is found.

So that means the router isn’t forwarding the ports to your devices. As others have said, it could be the ISP blocking it or it could be a configuration issue in the port fowarding.

Do you have any service listening on port 80? If not, I’d close it in the firewall and disable the forwarding in the router. Also sounds like a bad idea to set your router security to ‘low’, whatever that means for your router.

You can use a tool like this to check if your ports are accessible from the internet: https://www.yougetsignal.com/tools/open-ports/

Reading this again too, I like the suggestion to default power to 0. A lot of this was testing to see how to do it at a dumbed-down level; the Python file I was testing in is a lot messier as is!

The code is intended to only run mylcd.backlight(power) if the power variable was anything but 1 or 0, but the initialization was turning it on unexpectedly.

Yeh, that initialization was doing it. Not sure there’s a way to initialize it without powering it on, but at least I know!

A lot of the code I posted came from both trying to get a working test showing me if it got to the place I wanted as well as wanting a third option without multiple elif statements. I’m really just learning Python so lots of ways it could be better, I’m sure.

Found the problem, as mentioned in another reply. I really appreciate your response here though - I’m coming from a PowerShell scripting background with my day job, and learned about arguments in Python just this morning. I didn’t know about ‘choices’, but that’s super handy.

I had tried ‘is not None’ and didn’t have any luck so then tried == with the same outcome.

Yes, just got to testing again and that was it. The mylcd = I2C_LCD_driver.lcd() line is turning it on, then I need to action after it. I had tried using ‘is not’ before posting with no effect, and now I know why.

Sorry, what’s preventing you from adding the subdomains in the Vultr DNS?

deleted by creator

Was this green or yellow Chartreuse?

For me it’s that Tumblweed at least uses BTRFS by default, so rolling back to a previous snapshot is a breeze if needed.

Australia isn’t a good representation since it’s compulsory to vote; unless you’re suggesting Canada should enact laws doing the same.

Yes, that’s very different than the ‘pressing your thumb’ like you said in the message I was replying to.

Carving letters into the wood equals ‘pressing his thumb’ to you? Did you even read the article? Regardless, let me ‘press my thumb’ into your forehead and see if you think it’s fine, just let me be.

I tipped him well

I can’t tell if that’s supposed to be sarcasm, but if not you were encouraging his bad behaviour.

I’m happy for them to be posted here and see them, just wanted to mention my experience with the requirements since I don’t have a fanatical account.

It’s not just ‘sign up for a newsletter’ - I just tried, and it’s also ‘register an account and link your steam account’. Maybe this is just how it works for Canadians though, but either way it’s a big enough turn off for me to not bother.

So ‘it’s already on port 8080’ makes sense, but as I mentioned, no remote computers on the same LAN can reach that port (they can ping the host with no issue), and that’s what I’m trying to resolve. I’m not using a reverse proxy.

Through further testing it looks like I’d missed adding the firewall rule to allow port 8080 TCP to the public zone; I currently have it added it to the ‘trusted’ zone which came from some online guides regarding rootlet podman but that didn’t resolve it. I’m sure I’d added it to the public zone previously as well to test with it not working so removed it, but it is now so I’ll have to keep testing a bit to ensure it’s repeatable.

Sounds like you need to familiarise yourself with PowerShell and Group Policy.