using cloudflared to connect to our internal server

Got this message from PB:

Have done the following to do the cloudflare (ZeroTrust) tunnelling to ourservername. 

Cloudflare Zero Trust + Google Workspace + ourservername (SSH)

Architecture Overview

User (Client Machine)

        │

Cloudflare Access (Zero Trust)

        │

Google Workspace (Authentication + MFA)

        │

Cloudflare Tunnel (cloudflared)

        │

ourservername (SSH)

Authentication Flow Chart

User runs SSH (like ssh  ssh-ourservername.ourdomain.org)

        │

Cloudflare Access intercepts request

        │

Redirect to Google Login

        │

User authenticates + MFA

        │

Cloudflare verifies identity + policy

        │

Cloudflare establishes Tunnel

        │

Access granted to ourservername ssh

On the client machine 

Install cloudflared 

Create a config file in .ssh folder

$ ~/.ssh/config

Host ourservername

  HostName ssh-ourservername.ourdomain.org

  User ourusername

  ProxyCommand cloudflared access ssh --hostname %h

Then you the connection would be like

$ ssh ourservername

Connection was successful with ssh with the configuration as above. Connection was initially not successful with Filezilla. 

ChatGPT told me that filezilla does not understand the proxycommand instruction, hence we can run cloudflared in proxy mode by running this in a terminal:

cloudflared access ssh --hostname ssh-ourservername.ourdomain.org --url localhost:2244

This creates a local listener on localhost:2244 which forwards via Cloudflare to the remote SSH server

With this, Filezilla could connect to localhost 2244 successfully (and I could see the files on ourservername with Filezilla.)

OpenSpace - workarounds for toggle trails causing Pluto trail to appear

 Using the default action by pressing the 'T' key, Pluto trail starts to appear if we disable it before we start. 

One way might be to remove the Pluto Trail asset from openspace before starting the playback?

Another way would be to edit the recording to replace 

openspace.toggleFade("Scene.*Trail.Renderable");    openspace.toggleFade("Scene.*trail.Renderable");

with

openspace.setPropertyValue("Scene.*Trail.Renderable.Fade", 0, 1.0); openspace.setPropertyValue("Scene.*trail.Renderable.Fade", 0, 1.0)

openspace command convention

Quick note to self - when we want to use the built-in fadeIn or fadeOut commands, we can't use the name of the object as seen in the info tab - like Scene.Moon here,

We will get errors like
Error when calling script 'openspace.fadeIn': Could not find property 'Scene.Moon.Enabled'

Checking the script log, we need to append .Renderable to that name, like

openspace.fadeOut("Scene.Moon.Renderable", 5)

Edit - Note: All of the above were with respect to the 0.21.x version. In version 0.22, things may change - for eg this commit.

tumblerd prevents disk from being ejected on Linux

When trying to eject a USB external disk, a message along the lines of "process tumblerd is currently using the disk, eject anyway?"

https://duckduckgo.com/?q=what+is+tumblerd+which+is+keeping+disk+from+being+ejected+on+linux&ia=web

Since I had a very large number of images on that drive, and I had just saved an mp4 file onto the drive, tumblerd was probably creating thumbnails for all of the multimedia files. So, did 

killall -HUP tumblerd

and then the disk could be ejected.

OpenSpace session recording "save frames" crash

On my Lenovo ThinkCentre M93 machine with an NVidia GTX1050 graphics card, OpenSpace session recording playback with "save frames" was crashing after a few hundred frames being saved. Each frame was taking around 1000 to 1500 ms for 4096x4096 frames.

According to Claude.ai, the crashes might be due to CEF "being starved" between updates - and I submitted this fix as an issue on the OpenSpace repo.

Claude suggested workaround was in SGCT.

// sgct/src/image.cpp

png_set_compression_level(png, -1);  // changed to:

png_set_compression_level(png, 1);

As the comment just above that line says, -1 sets the compression level to default, which seems to be 6. Setting this to 1 made the frame export only 300 ms per frame (3x faster) and also fixed the crashes - so CEF was not "being starved" of updates.

The increase in file size was not much, 4 MB increased to 5.1 MB for a typical frame.

Another change I made before exporting again, was to close all other windows and apps like the Edge Browser, which I had used earlier for triggering the exports - now OpenSpace has some checkboxes in the export settings which allows us to hide the UI while exporting, so we don't need to trigger the export via a web browser.

Edit: No, the problem is not solved. No crash when saving frames for this recording, ts_003_moon_to_Earth.osrectxt

but crashes after a few hundred frames when saving frames for this recording, ts_002_india_rotate_zoom.osrectxt

So my current workaround was to split the recording into multiple smaller recordings.

Edit - another workaround to get around the crashes, which seem to be caused by CEF, seems to be to disable the module CEFui inside OpenSpace > Settings - issue thread is at https://github.com/OpenSpace/OpenSpace/issues/3954 

uninstalling ollama

https://github.com/ollama/ollama/issues/986

ran all the lines suggested there, got some 15 GB freed.

Copy-pasting from the above,

Here's a general guideline on how to uninstall it:

Delete the Ollama binary:

Use the rm command to remove the Ollama binary. For example:

sudo rm /usr/local/bin/ollama

If the script created a systemd service, disable and remove it:

If the script created a systemd service for Ollama, you should disable and remove it using the following commands:

sudo systemctl stop ollama

sudo systemctl disable ollama

sudo rm /etc/systemd/system/ollama.service

sudo systemctl daemon-reload

Remove any created user and group (if applicable):

The script might have created a user and group named "ollama." You can remove them using the following commands:

sudo userdel ollama

sudo groupdel ollama

-----------------------

More lines from other people, esp if location of ollama and downloaded models are different - 

sudo rm -v /usr/local/bin/ollama

sudo rm -rv /usr/local/lib/ollama

sudo systemctl stop ollama

sudo systemctl disable ollama

sudo rm -v /etc/systemd/system/ollama.service

sudo systemctl daemon-reload

sudo userdel ollama

sudo groupdel ollama

sudo rm -rv /usr/share/ollama

# for downloaded models

rm -rv ~/.ollama

sudo rm -rv /usr/lib/ollama/

sudo rm -rv /usr/local/lib/ollama

domain transfers - godaddy to nettigritty and one account to another

We had a few domains which needed to be transferred. A couple of domains needed to be transferred from one account to another on nettigritty, and a domain needed to be transferred from godaddy to nettigritty.

downloading from a server via http (no SSL) with auth

Downloading some planetarium files from a server in Sweden, which had password protected directories but no SSL (no https) - 

1. Directly downloading via the browser - slow, prompts us to "Keep" or delete the file every time due to being downloaded unsecurely
   
   
2. Using aria2 - 
   
    aria2c -x16 -s16 --http-user=USERNAME --http-passwd=PASSWORD url
   
   Need ProtonVPN, since without it, http downloads are severely throttled to less than 100 kbps.
   
   
3. Better option, running 
   
   aria2c -x16 -s16 --http-user=USERNAME --http-passwd=PASSWORD -i urls.txt
   
   on one of our AWS servers - all the URLs get downloaded in a jiffy, then we can use Filezilla and download to our local machine over sftp without throttling issues.

change of email id in CMS

One of the users in our CMS (google apps script with php/pgsql authentication) changed their email id in the profile, but was then unable to find any of the assets they had been working on.

Now changed the 'username' field in the postgresql database for this user from

old@gmail to new@new.email

(the email id field had already been changed by the user.)

That seems to have solved the issue. This is a duplicate of an earlier post, https://hnsws.blogspot.com/2024/06/unable-to-see-old-assets-after-email.html

OpenSpace - hover over a planet and allow it to rotate under you - OpenSpace seminar

As noted in an earlier post (which I had forgotten), the relevant option is in Settings > Navigation Handler > "Follow Anchor Node Rotation" 

When I asked Gemini via aistudio.google.com, it found a transcript from an OpenSpace seminar, which is a useful link - https://www.ppadomes.org/events/online-seminars/ppsarchive/2025-archive/2025-01-31-chat