Can't login to ServerOne - LAN or remote

General
9

Monitor plugged and keyboard plugged it. Everything looks perfect! It took a while to boot, but it came to the login, accepted the password and “Connected”. Just did Electrs update and now backing up.

The problems seem to start with one of the recent OS updates.

Just tried to login to ServerOne remotely (Firefox/Onion) on Linux Mac Books and still getting “Hmm, We’re having trouble finding that site.” Was working great about a week ago.

So, it seems to me its something in the operating systems or browsers or both that blocking access. I will go back to the check list and continue where I left off

10

OK, so your server is fine. But did you check whether an IP address was assigned and a connection was established under System->About? I get a sense that you’re doing each step in half measures and not getting conclusive answers.

If you did check everything, then either your networking setup is flawed, or your client setup is flawed.

I’m still not sure you’ve completed all of these steps:
https://docs.start9.com/0.3.5.x/support/common-issues

…but if you have, you’ve missed something or you have an issue with your network.

Both your clients and your server have to be connected to the same router, they have to have IP addresses on the same subnet, they have to be able to communicate with each other.

11

Thank you StuPleb. You are correct that I have not completed the steps in Common-Issues. In one of my last posts I shared that I would go back to resume going through the steps on Common-Issues. I went deep into step six on checking the router, but I think that was worthwhile since it verified that the router was not the problem.

If I am going only half measure and not getting conclusive answers, it is due to my ignorance and thinking that I am getting the conclusive answer. Please forgive me for that. On the other hand, I think I was pretty conclusive regarding the router being in question.

Which “System” do I check on this? The Apple OS? Please forgive me but I’m not clear on this question/directive. Would you please give me more specifics on this?

12

In StartOS.

What I want to see is when you connect a monitor to the server, and you go to System → About in StartOS (after logging in), is whether there is an IP address assigned.

Don’t screenshot this, because the .onion address is right there too, and that’s private, but you can post the internal IP address. (likely 192.168.x.x)

Then also grab me the IP address of the computer you’re using now.

Confirming this will eliminate at least one of my suspicions.

13

In ServerOne>About>Web Addresses I see
Tor
LAN
eno1(IPv4) - this has an IP address
eno1 (IPv6)- n/a
wlp0s2Of3 (IPv4) - n/a
wlp0s20f3 (IPv6)- n/a

I’m on the Mac Book/Linux Mint. I entered the only IP address in the browser and I got a StartOS page: Trust Your Root CA

I will update you after I go through this process.

14

Since I was able enter that IPv4 address, the only one in ‘About’, and that took me to a StartOS page, does that confirm that the IP address was assigned?

Trust Root CA was the page that came up.
I went through the process of downloading trusting the root CA. When I downloaded, I saw that it was the 4th copy of that download, which confirmed to me that my memory was right in that I’ve done this before and walked through the steps.

I see when I open the file from Download, the [adjective-noun].crt it looks good, but, at the bottom there are 2 options, Close and Import. Import is grayed out and not active - I can’t select to import, I can only Close.

I went forward on 'Trusting Your Root CA on Linux", entering all the commands and it said at the end “1 Added”, which the directions say is success. Then I went to “final step” on Firefox and “security.enterprise_root.enabled” was already “true”, since I’ve done this a few times before.

As per directions, I went back to the page that came up when I entered the IPv4 address and the last step there was to refresh the page. The refreshed page came up exactly the same. In the browser address bar, the IP address was the same and it still had the icon of a lock with a red diagonal line through it, indicating not private or secure.

At the bottom of the page, there was an option to skip Trust Your Root CA. I hit ‘skip’ and got the “Warning: Potential Security Risks Ahead” message. This indicates to me that the Root CA is not working.

I suspect it is that place in Downloads where I can see the crt, but can’t import it.

What am I not doing right? What am I missing?

15

When following the instructions for Configuring Firefox to Respect Your Root CA, make sure to click on the correct tab for your Linux system. This will give further instructions needed in your case.

Screenshot from 2025-03-01 21-14-10
Screenshot from 2025-03-01 21-14-101118×783 154 KB

16

Thanks Alvaro. I missed that step earlier. Did it on Mint Linux laptop and now can access ServerOne on LAN with Mint-Firefox.

Can also access on ServerOne on Lan on Mac Mini.

Still can’t access remotely. I will go to the next step on “Config Firefox for Tor”.

1 Like
17

Pasting your private .onion into Tor Browser is a quick and easy way to confirm whether things are working or not. You can then make the decision of whether you even need to configure anything else.

18

Thank you StuPleb. It’s been 12 days and I’m just getting back on this. Yes, I just pasted the .onion into Tor now and it worked!! YAY! And, I just now pasted it into Firefox that I initially set up when I got the Server and it also is working!! I was trying this many times earlier in Tor and Firefox up to a few days ago and it would not allow me to go forward. I would get the “Hmm, we don’t recognize this…”
I don’t know what happened, maybe the computer gods decided to heal my computer issues. Anyhow, Thank you STuPleb and others who have been helping me. I appreciate you all.
I will now try it on the Linux Mint machine and see if it works there now. It did not yesterday, but today’s a new day apparently.

19

I can now access the ServerOne on Tor, Firefox and in the LAN on the Mac MIni.

I can now access the ServerOne on Tor and the LAN on the Mint Linux laptop, but not on Firefox. Still getting “Hmm, we’re having trouble finding this site. …”

20

So you have an issue specific to Firefox on Linux?

21

Yes, but I haven’t gone through all the steps we discussed earlier. I’ll let you know when I succeed or need your help. Thanks Stu

22

You may need to install and configure Avahi. You can see here for more discussion on this.

23

Thank you Alvaro. I thought I may have missed this step, but I did not. When I went through it as you advised, I saw that I had System CA Trust Module already installed. But I unloaded that and re-installed it again. After restart, I tried to access ServerOne remotely, but still got the same “Hmm, we’re having trouble finding that site. …”

24

Yes, still having issues with Firefox to access ServerOne remotely. Tor works, but it does not recognize my CA Root and give me all the warnings that I will die a horrendous death in the swamp forest.

As I mentioned to Alvaro, I went through the steps for Security Devices and re- installed the System CA Trust Module, but Firefox still will not load the ServerOne remotely. At the top of those instructions it says
"Tip

The path to p11-kit-trust.so will be slightly different if your processor’s architecture is not x86_64."

I don’t know if this applies to this computer or not. Here’s what I have:

System:
Kernel: 5.15.0-134-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 6.0.4
tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia
base: Ubuntu 22.04 jammy
Machine:
Type: Laptop System: Apple product: MacBookPro9,2 v: 1.0 serial: Chassis:
type: 10 v: Mac-6F01561E16C75D06 serial:
Mobo: Apple model: Mac-6F01561E16C75D06 v: MacBookPro9,2 serial:
UEFI: Apple v: 425.0.0.0.0 date: 10/26/2021
Battery:
ID-1: BAT0 charge: 29.6 Wh (54.7%) condition: 54.1/62.9 Wh (86.0%) volts: 11.2 min: 10.9
model: DP bq20z451 type: Li-ion serial: N/A status: Discharging cycles: 1396
CPU:
Info: dual core model: Intel Core i7-3520M bits: 64 type: MT MCP smt: enabled arch: Ivy Bridge
rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 4 MiB
Speed (MHz): avg: 1197 min/max: 1200/3600 cores: 1: 1197 2: 1197 3: 1197 4: 1197
bogomips: 23148
Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel 3rd Gen Core processor Graphics vendor: Apple driver: i915 v: kernel ports:
active: LVDS-1 empty: DP-1, DP-2, DP-3, HDMI-A-1, HDMI-A-2, HDMI-A-3, VGA-1 bus-ID: 00:02.0
chip-ID: 8086:0166 class-ID: 0300
Device-2: Apple FaceTime HD Camera type: USB driver: uvcvideo bus-ID: 1-1.1:3
chip-ID: 05ac:8509 class-ID: 0e02 serial:
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting unloaded: fbdev,vesa
gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1280x800 s-dpi: 96 s-size: 338x211mm (13.3x8.3") s-diag: 398mm (15.7")

There’s a lot more of that system stuff, but I didn’t paste it here thinking it’s not needed for this. If you want it, tell me.

I am going through "Configuring Firefox for Tor and I see at the top of the instructions
"Caution

If you cannot connect after following this guide, your Firefox may be installed in a jailed environment, such as an AppImage, Flatpak, or SNAP. Please try an alternate install method that does not isolate Firefox from the regular filesystem."

This Firefox may be a “Flatpak” install. I will continue go through the Config. Firefox for Tor and it that doesn’t work I will unistall Firefox and reinstall without Flatpak.

25

I am holding off on this until I complete Config Firefox for Tor and, if that doesn’t work, reinstall Firefox without Flatpak. If all of the above is correctly installed and it still doesn’t work, I’ll install and config Avahi. Please advise if you see me on the wrong path to a solution.

26

A Success: I tried to install in Tor under Security Devices “System CA Trust Module” like I did in Firefox, but Tor said it would not accept that. But in reality, it did and now I’m in Tor remotely without the warnings.

Firefox still not loading Server One remotely.

27

This is all good, no issue here.

28

If everything is working in every single conceivable way other than Firefox… then sure… install the non-flatpak and see what happens…

sudo add-apt-repository ppa:mozillateam/ppa && sudo apt update

on Mint you will probably need to do…

echo -e "Package: firefox*\nPin: release o=LP-PPA-mozillateam\nPin-Priority: 1001" | sudo tee /etc/apt/preferences.d/mozilla

then

sudo apt install firefox