connection has been gracefully closed tightvnc что значит

Что там нужно настроить? Можно ли реализовать подключение без ssh?

>[оверквотинг удален]
> ошибка: Connection has been gracefully closed.
> Что делал, разрешил удаленное Администрирование VNC, в сетевых службах xinetd менял пользователя
> на root, закомментировал строку в host связанную с ipv6, переустанавливал TigerVNC
> и x11-xtorg.
> Как можно все таки заставить VNC работать?
> Строго не судите, первый раз настраиваю OpenSuse.
> Черный экран как при подключении на 5901 порт, так и через браузер
> и яву на порт 5801.
> Скриншоты по ссылке https://yadi.sk/d/DOFQP5zS3CbJU6
> Помогите пожалуйста все перепробовал уже.

Поставьте X2Go Server на сервер,
X2Go client на клиентскую машину.
Подключайтесь, он работает через ssh.

>[оверквотинг удален]
>> и x11-xtorg.
>> Как можно все таки заставить VNC работать?
>> Строго не судите, первый раз настраиваю OpenSuse.
>> Черный экран как при подключении на 5901 порт, так и через браузер
>> и яву на порт 5801.
>> Скриншоты по ссылке https://yadi.sk/d/DOFQP5zS3CbJU6
>> Помогите пожалуйста все перепробовал уже.
> Поставьте X2Go Server на сервер,
> X2Go client на клиентскую машину.
> Подключайтесь, он работает через ssh.

А штатными средствами
через x11-xtorg нет возможности заставить работать?

>[оверквотинг удален]
>>> Строго не судите, первый раз настраиваю OpenSuse.
>>> Черный экран как при подключении на 5901 порт, так и через браузер
>>> и яву на порт 5801.
>>> Скриншоты по ссылке https://yadi.sk/d/DOFQP5zS3CbJU6
>>> Помогите пожалуйста все перепробовал уже.
>> Поставьте X2Go Server на сервер,
>> X2Go client на клиентскую машину.
>> Подключайтесь, он работает через ssh.
> А штатными средствами
> через x11-xtorg нет возможности заставить работать?

Была такая ситуация с черным экраном по VNC OpenSuse 42.1 на сервере ibm x3550 m4.
Так и не смог ее победить. В то же время OpenSuse 42.1 был установлен на обычный пк (с простенькой видеокартой) и все прекрасно отображалось по VNC. Cервер после был переведен на Centos 7, там не было таких проблем с VNC, но предпочел использовать X2go. Думаю проблема в драйвере видеокарты + настройки x11.

>[оверквотинг удален]
>>> Подключайтесь, он работает через ssh.
>> А штатными средствами
>> через x11-xtorg нет возможности заставить работать?
> Была такая ситуация с черным экраном по VNC OpenSuse 42.1 на сервере
> ibm x3550 m4.
> Так и не смог ее победить. В то же время OpenSuse 42.1
> был установлен на обычный пк (с простенькой видеокартой) и все прекрасно
> отображалось по VNC. Cервер после был переведен на Centos 7, там
> не было таких проблем с VNC, но предпочел использовать X2go. Думаю
> проблема в драйвере видеокарты + настройки x11.

Спасибо! А драйвера я и не ставил, системные какие установились те и работали. Попробую с драйверов начать, если не поможет установлю X2go.

>[оверквотинг удален]
>>> через x11-xtorg нет возможности заставить работать?
>> Была такая ситуация с черным экраном по VNC OpenSuse 42.1 на сервере
>> ibm x3550 m4.
>> Так и не смог ее победить. В то же время OpenSuse 42.1
>> был установлен на обычный пк (с простенькой видеокартой) и все прекрасно
>> отображалось по VNC. Cервер после был переведен на Centos 7, там
>> не было таких проблем с VNC, но предпочел использовать X2go. Думаю
>> проблема в драйвере видеокарты + настройки x11.
> Спасибо! А драйвера я и не ставил, системные какие установились те и
> работали. Попробую с драйверов начать, если не поможет установлю X2go.

Через X2go так же не подключалось. В итоге все снес и поставил OpenSuse 13.2 и там VNC заработало.

>[оверквотинг удален]
>>> ibm x3550 m4.
>>> Так и не смог ее победить. В то же время OpenSuse 42.1
>>> был установлен на обычный пк (с простенькой видеокартой) и все прекрасно
>>> отображалось по VNC. Cервер после был переведен на Centos 7, там
>>> не было таких проблем с VNC, но предпочел использовать X2go. Думаю
>>> проблема в драйвере видеокарты + настройки x11.
>> Спасибо! А драйвера я и не ставил, системные какие установились те и
>> работали. Попробую с драйверов начать, если не поможет установлю X2go.
> Через X2go так же не подключалось. В итоге все снес и поставил
> OpenSuse 13.2 и там VNC заработало.

Может быть. Главное все работает и это хорошо) Спасибо за помощь!

Источник

Error «Connection has been gracefully closed» trying to vnc to Ubuntu v20.04

I am running Ubuntu Server v20.04. I am a Linux noobe. I want to be able to TightVNC into my Ubuntu Server (from Windows 10) to perform file management (via XCFE Desktop) and run process’ from the console that will continue to run even though I disconnect my putty connection. I have putty v.074 and xMing v6.9.0.31 Installed on my Windows Desktop. I added some details below. Any help is appreciated

I followed the process documented here, The error I get is «Connection has been gracefully closed»

I installed VNCServer v1.3.10-0ubuntu5 using the process below.

I opened a firewall port using UFW using this command (sudo ufw allow from 192.168.1.0/24 to any port 5901). The output to «sudo ufw status verbose» is shown below:

9 Replies

wanman0621 ​Just curious to know if you actually need a GUI connection to your server or if an SSH session would work for you?

Personal preference, if you want to leave a process running on your LInux machine, just SSH to it and make use of the «screen» utility. Install it if it’s not already there.

At the command line, you can just type screen and you’ll have a session that can be resumed at any time which will not disconnect along with your SSH session!

]$ screen Will take you into a new screen session. Initiate your process and then disconnect from the active screen session using a d

If you have multiple screen sessions open, you’ll be prompted as to which one you want to connect to:

Way easier than leaving your production server exposed.

Thanks for your reply. This is awesome. I did not know about this capability and will use this moving forward for certain things.

However, I really need a GUI because I have thousands of files to manage and reorganize. This type of work is easier done with a GUI File Manager. Also while I am moving GBs’ of files around, I need the session to stay open even when I disconnect from SSH. This is why I want to Remote Control The Console.

I am using a method that uses a tunnel as I mentioned in my thread. This seems to be the most secure method from what I am reading.

Any advice on how to resolve the error I described? Or is there another way to do this?

However, I really need a GUI because I have thousands of files to manage and reorganize. This type of work is easier done with a GUI File Manager. Also while I am moving GBs’ of files around, I need the session to stay open even when I disconnect from SSH. This is why I want to Remote Control The Console.

You should post (perhaps in a new thread) the nature of the work that you are trying to do. It might be a lot easier to accomplish via command line, versus a GUI.

For instance, depending on the definition of «move,» «moving GBs’ of files around» is something that should happen nearly instantaneously, and you may not have to have a process grinding away after you’ve disconnected.

This is a Plex Media Server with 8TB of media located all over the place. I have two raid groups and 2 lvms setup with different mount points for different types of media. Moving data within a mount point is quick, but from mount point to mount point or volume group to volume group it takes much longer. There are times where i have to transfer 400GB of media files from one place on the drive to another. And there are times when I have to transfer 1 file totaling 2GB to another location. These files should’ve been placed properly to begin wit, but its a mute point now.

If there is a better solution than remoting to the console and using the gui, Im willing to hear it. Or if you can help me figure out the error that Im getting, that would be great.

Again, not altogether sure why a GUI is needed for this?

Inside an SSH session, you can issue a copy or move command which would do the trick right? So then start a screen session, kick off the copy and then disconnect your screen session using a d

The screen session will never close unless you terminate it.

Sorry I can’t help with the VNC error.

This is a Plex Media Server with 8TB of media located all over the place. I have two raid groups and 2 lvms setup with different mount points for different types of media. Moving data within a mount point is quick, but from mount point to mount point or volume group to volume group it takes much longer. There are times where i have to transfer 400GB of media files from one place on the drive to another. And there are times when I have to transfer 1 file totaling 2GB to another location. These files should’ve been placed properly to begin wit, but its a mute point now.

If there is a better solution than remoting to the console and using the gui, Im willing to hear it. Or if you can help me figure out the error that Im getting, that would be great.

I’m not saying that a remote shell is better than a remote gui for your task. It’s just the thing that I know. That is, if my only tool is a hammer, I’m happy pounding on that, even if it’s a screw. 🙁

Nonetheless, I’d say that Random-SPUSER is onto something.

You might want to consider using rsync to copy data from one filesystem to the other, especially if the files are not static. In that case, subsequent passes of «rsync» will only pick up the changes (and run much faster). Once you’re confident that everything is in place, you can remove the data from the original filesystem. If applications expect to find data in the original location, you could use symbolic links in the original filesystem that point to the new location.

If the «file» utility can reliably distinguish between your media types, you might be able to script a copy, or rsync, that works through entire directory trees using «find». The same would apply if the filename reliably gives you the media type.

From a command line, you can tell any command to run in the background simply by appending «&». When logged in via «ssh», that should keep your process running after you disconnect. If not, you can tell the process to continue after logout by prefixing your command with «nohup», which tells the command to continue, even after you’ve disconnected.

Источник

Connection just gets closed on windows #930

Comments

danielocdh commented Jan 1, 2020 •

Describe the bug
Connection gets closed right after being made on windows 10 1909

To Reproduce
Steps to reproduce the behavior:

Expected behavior
VNC server/viewer to connect normally

Client (please complete the following information):

Server (please complete the following information):

Additional context
Edit: I just tested with version 1.9.0 from bintray without any other change, everything works, I’ll use that for now.

The text was updated successfully, but these errors were encountered:

samhed commented Jan 2, 2020

Could you check the VNC server log? I’m not sure how it works on Windows, but I believe you should be able to find it here:

If that file doesn’t exist, you might have to start the VNC server with this argument «-Log *:file:100», make sure the directory C:\temp is created before you start it.

klui2k1 commented Jan 3, 2020

I’m experiencing the same thing. If I go back to 1.9.0 x64 things work fine. Server is running under Windows 10 1909 x64. The system was upgraded from Win7 to Win10. Client is also an upgrade from Win7 to Win10, also 1909 x64.

The logs show the following. Important tidbits at 16:03:21. I don’t remember what I did to cause the logs afterwards except I was looking at the settings and then exited winvnc4.exe. Reinstalling is not an option for me.

danielocdh commented Jan 3, 2020

I think I got different results than @klui2k1

This is a headless system, but the issue happens with or without monitor. I plugged in a monitor and restarted before doing these tests.
I used «vncviewer64-1.10.1.exe» as client for both tests
*.err.log came from using server version 1.10.1
*.ok.log came from using server version 1.9.0

CendioOssman commented Jan 3, 2020

Thanks for the logs, @danielocdh. I think I see what’s wrong. Let me see if I can fix it.

@klui2k1, you seem to have a different issue. Could you file a new issue for your problem? Please include log files from both the working and broken WinVNC as well as much details as you can about your setup.

mrbbs commented Jan 3, 2020

I have the same issue as danielocdh. We would like to change from the security flawed UltraVNC to TigerVNC.
We did a clean install on a Windows 10 1509 pc as server (v1.10.1) with the latest 1.10.1 client.
After clicking connect the VNC Viewer window disappears.

CendioOssman commented Jan 3, 2020

The relevant log line was this:

VNCSConnST: closing 192.168.1.85::64421: setSize not supported

Should be fixed as of 7301491. If you can do your own builds then go ahead and build that. Or you can wait for the next nightly build and try that.

Thank you for reporting.

wizeman commented Jan 15, 2020

Would it be possible to make a new release with this fix?
The Chocolatey repository has the latest release but due to this bug the TigerVNC server is completely broken. I know the nightly build should work but nightly builds don’t usually get packaged in Chocolatey.

jamieburchell commented Jan 19, 2020 •

I’ve started experiencing an issue connecting to TigerVNC (service) on Windows 10.0.17763. The client I’m using states that the connection was unexpectedly closed. This appears in my log file:

VNCSConnST: closing 10.37.9.17::50367: setSize not supported

I upgraded TigerVNC to the latest version (tigervnc64-1.10.1.exe) but this version exhibits the same behaviour for me. I can’t work out why this has just started happening.

Edit: I’ve switched to TightVNC server for the time being, which appears to work.

jamieburchell commented Jan 20, 2020

CendioOssman commented Jan 20, 2020

A simple rebuild won’t help unfortunately as we also need the fix in #930. So we need to roll up a new release in that case.

johnwmail commented Mar 19, 2020

where can I download the new version with this fix?

robin92 commented Apr 1, 2020

Please release a patched version for Windows already. This is making TigerVNC unusable since December!

deedubb commented Apr 8, 2020

404 Not Found
Code: NoSuchKey
Message: The specified key does not exist.
Key: nightly/index.html
RequestId: 6B77FB98C0934A54
HostId: IWtNg8Xy5wXBit69i05yDDsNdeieUEhHZU+SQTdG0MOgDh722Rt67eA5ihZ5FOBj30SLVv5xW+w=

Can anyone post tigervnc64-1.10.80.exe while they fix this?

robin92 commented Apr 8, 2020

Note that I had some issues with cursor position mapping across VNC connection. In reality it was unusable. Could you check if this is the case for you as well?

mdPlusPlus commented May 17, 2020 •

Is there a reason there are still no fixed stable binaries in May?
The nightly site provides unsigned binaries over a http connection. Not exactly ideal.

Edit: Not in June either.
Edit: Neither in July. Seven months since a broken «stable» release and the nightly page errors out. 👍
Edit: Maybe August? Nope.
Edit: End of August and atleast we have a beta release. Hooray, I guess.

btrower commented Jun 21, 2020

MarkMielke commented Jun 23, 2020

I don’t think it is old spaghetti code. The main limitation is that the community supporting the tool is small, and the people with itches to scratch and the means to do so are few.

It’s easier to rant than to solve problems.

Putting aside the rant. have you tried the nightly build for Windows, that is being built, and does it resolve your issue? In many cases I have found the nightly build perfectly acceptable for use.

Источник

TightVNC

Brought to you by: anton19286, const_k

Group

Searches

#1386 Connection has been gracefully closed when try to connect to other computer window 7

I installed the latest tightVNC version 2.8.2.1 but when i try to to connect to other computer from my other computers. It would prompt for a password and i will type correct password so then say, «Connection has been gracefully closed.»

I tried restarting the VNC service, rebooting, reinstalling TightVNC. Nothing worked.plshelp me:(

Related

Discussion

I just sent to file dump for you by email,pls help me check with thank

Please, try this binaries. What Windows 7 version was used? Has yours server one or two displays?

Hi,
I have the same message but not exactely at same time. I let you to see if there is something in relation with the problem exposed here, or if it may help :

When I try to connect to a remote computer that is using changeip dyndns (managed and updated by an SFR box),
— if I use the changeip.net subdomain (xxx.changeip.net), I always get «Connection has been gracefully closed» after a few seconds time-out, before the login form apears.
— If I retrieve the IP of the remote computer from a ping to the same subdomain and then try to connect with IP address, each time I can connect without any problem.

Connection has been gracefully closed message just means the connection was closed by server

I’m also having this issue at least on one laptop with version 2.7.10 and 2.8.2.1 (64bit). I attached the crash.dmp file.
The laptop has an additional displaylink driver installed which was not in use during the test.

This is the logfile.

Источник

TightVNC

Brought to you by: anton19286, const_k

Group

Searches

#180 Error: Connection has been gracefully closed

Been using tight VNC for many years it is a great product. Have installed it on many computers without issue until today. Got a new laptop and installed the version 2.8.27 to match my desktop. I use the Tight VNC Viewer on my Desktop computer to connect to a few computers in my office. I can connect to all of them fine except for the new laptop. The hostname for the laptop is Sales-LT2 I use the Port 2500 for the Main Server port on the laptop Tight VNC Service Configuration dialog. On my desktop I open the TightVNC Viewer and use «SALES-LT2::2500» to connect and I get a notification dialog that reads «Connection has been gracefully closed» I cthen click the ok button and the dialog closes and thats all I get. I looked at the firewall settings on the laptop and it shows that the TightVNC application is allowed through Domain, Public & Private. What are my next steps? The laptop is using Windows Professional version 1909 with all updates current as of 5/6/2020 OS Build 18363.815

My local network is on a local domain using an OPNSense router/firewall device. But since I’m trying to connect a local computer to a local computer that device should not interfer. It hasn’t with any other computers that I connect to.

I have attached two logs from C:\Programdata\TightVNC Directory

What is my next step in solving this issue? Any help with this would be greatly appreciated.

Discussion

I should also note that I used the laptop Ip address as well in the TightVNC Viewer like «10.14.1.60::2500» and that produced the same result.

Ok So another thing that I forgot to mention is that TightVNC Service Configuration dialog on the Access Control tab, there is Rules box. I have two rules set up in this box the 1st rule was Deny 0.0.0.0 to 255.255.255.255 and then I added an Allow rule 10.14.0.0 to 10.14.7.255 for our local domain. What I did not realize when I added these two rules is that it makes a difference of the order that thay are added. I added the Deny rule 1st the the Allow rule. This was backwards, 1st you have to add the Allow rule, then the Deny rule. Otherwise it blocks everything. This is why I could not connect. This is a good lesson in following documented procedure to the letter and why it is important. I wasted two days on this to discover it was an error that I made myself. Hope this helps others that may come across this same thing.

Hi!
first uninstall, clean HKLM\software\TightVNC\Server
reinstall and try to make connection from the same computer (enable Allow loopback in configuration), set loglevel 9 and send the log to support@tightvnc.com

@anton19286 If you read my previous message, you will see that I have it working now. I had my allow and deny rules out of order and that is what was causing the issue. Since I moved the allow rule to the top of the list everyting works fine now.

Источник

• ← connection has been closed rage mp что делать
• connection lost reconnecting rage mp что делать →