127.0.0.1 is your own machine… called localhost ??
I wonder are Mega and Protonmail using the same port number… 8080 . That would explain a lot.
@nevj I don’t think so. The bridge shows 127.0.0.1 port 1143 for IMAP and port 1025 for SMTP. The only reason I learned about the 8080 for Mega, I assume, is that the only thing I can access in Mega during this issue when I hit settings is the proxy setup and I could see that the port was 8080. Then I ran the ufw commands and saw a previous rule for allowing 8080–so I assume when Mega installed initially this port was added through the firewall in LM.
It is my understanding that Timeshift restores the OS to a certain state, which would include the localhost settings? Should I run that back to say Sunday and see if that fixes it?
Thanks,
Sheila
1 Like
No harm in trying. You can always run it forward again.
I dont understand how localhost is involved in this?
I think it has to be some sort of networking issue
I don’t either, that is why I hesitated to even mention it at first. But why would I get that message in Kubuntu about not connecting even though email was coming through as I watched Thunderbird in that OS? And why would Mega stop working in both suddenly? I am at a loss, as Mega support also is.
I haven’t used Timeshift in a long time, so let me attempt that in LM. But I swear, if that fixes Mega in both… I hate not knowing the “why” and would not know how to compare anything before & after to see what changed.
Sheila
If the fault is with Protonmail, I doubt if timeshift will help. Have you tried just using maybe Gmail instead of Protonmail?
Let’s not go there. I require secure, private email and host my business emails on Protonmail.
Sheila
Me too.
We are not even sure this fault is in your system
You said both LM and Kubuntu have the fault.
That seems to say the fault is elsewhere
My best advice would be to contact Protonmail!!!
Nev,
Should I take screenshots of all the changes to be made reported after the dry run in Timeshift? Would that maybe help narrow down the culprit if it does get fixed with the restore?
Sheila
Protonmail is not going to do anything since it is working. Trying to tell them their outage affected my computer with Mega would get me nowhere. Believe me, I thought about it.
Sheila
If you run timeshift, it will take you back, but as soon as you run your updates you will be right back where you started from, I see this as a no-win situation, when the issue is with Protonmail.
That’s IF any updates caused it. What if when the Protonmail server went down it did some change to my localhost file(s) and that change would now not be present? System updates would not affect that and I may be wrong, but I do not think LM updates caused this. It’s just strange to me that Mega stopped working exactly when the Protonmail server went down. But even though Thunderbird & Protonmail bridge are now working since it came back up, Mega never started working again.
Sheila
Not sure .
Yes. I understand, and I never said updates are responsible, but Protonmail is !!! But until you find what has changed with your loacalhost file then you are just chasing the wrong rabbitt. @nevj could give more advice than I can but something has changed with your networking, without your knowledge.
You need to ask protonmail, did they change anything.
I started with the screenshots, but there were way too many. I have finished the restore and mega did not autostart, which it always did before. I may try going back one week earlier just to be sure…
If what @4dandl4 says about networking changed and the host service file, how would I check that? Should I try connecting to a different network (say use my phone as a hotspot with Verizon network) and see if that fixes anything? Not sure what is meant by “network” other than that.
Sheila
Nev,
Forgot to mention that in addition to not autostarting, Mega still had the issue. And that was a day before the Protonmail server went down.
Sheila
I went back in time to 07/18/23, a week before, and mega was not yet installed for some reason, but found the downloaded file and installed. Same issue occurred. So now I am shifting back to this morning before I ever restored in Timeshift,.
That tells us as @4dandl4 predicted, it does not fix the issue. So I am at a loss other than to wait on Mega support (not hopeful) to see if they can resolve it.
Thanks,
Sheila
And, from personal experience, if you keep using timeshift it will break your system.
Do not believe the issue is with “Mega”
What is in your " sudo nano /etc/hosts " file"
@4dandl4 hang on, restoring LM to this morning’s state.