5.10.1 spawn many "unable to connect to localhost" popups

RUMlog, the Next Generation. Completely rewritten.
SO9W
Posts: 12
Joined: Sun 13. Nov 2022, 12:50

5.10.1 spawn many "unable to connect to localhost" popups

Unread post by SO9W »

Hi. I'm using recent version of RUMlogNG. During a startup or when any window is opened it spawns "unable co connect to localhost server" message popup. You can see it here:

Someone have any idea what is happening?

Version 5.10.1 (546)
macOS ventura 13.0 (22A380)
User avatar
DL2RUM
Administrator
Posts: 2931
Joined: Mon 27. Aug 2007, 13:36
Location: JO40DF

Re: 5.10.1 spawn many "unable to connect to localhost" popups

Unread post by DL2RUM »

What is the full text from the box?
73 and best dx de Tom, DL2RUM
SO9W
Posts: 12
Joined: Sun 13. Nov 2022, 12:50

Re: 5.10.1 spawn many "unable to connect to localhost" popups

Unread post by SO9W »

It's in polish - I suppose it comes from system translations, it says:

"Wystąpił problem podczas łączenia się z serwerem „localhost”. Być może ten serwer nie istnieje lub jest w tym momencie niedostępny. Sprawdź nazwę serwera lub jego adres IP, upewnij się, że połączenie z siecią działa prawidłowo, a następnie spróbuj ponownie."

what means

"there was an error during connecting to localhost server. Maybe that server do not exists or is unavailable..."
Zrzut ekranu 2022-11-13 o 14.53.48.png
User avatar
DL2RUM
Administrator
Posts: 2931
Joined: Mon 27. Aug 2007, 13:36
Location: JO40DF

Re: 5.10.1 spawn many "unable to connect to localhost" popups

Unread post by DL2RUM »

This is not a RUMlog message. Can you post a screen shot from your Network window?
73 and best dx de Tom, DL2RUM
SO9W
Posts: 12
Joined: Sun 13. Nov 2022, 12:50

Re: 5.10.1 spawn many "unable to connect to localhost" popups

Unread post by SO9W »

Yeah seems it's related to network shares.

My RUMLOG.rlog file is placed on Google Drive. I'm using Google drive application - it lets me set some folders, like this with log database, to have local copy on disk drive.

Once I've created new, empty log on local drive, and re-opened log from google drive again problem disappeared.

Issue was confusing, because log was opened as usual, I could write to it and so on.

Thanks for reply, and thanks for creating this great application.
Post Reply