Centos and vnc problem

[SmaTTeR]

So I bought a VPS to run bots on and installed Centos 5/6 on it, installed vnc java and all that good stuff. But for some reason every time I reboot the VPS it won't let me connect via PuTTy or VNC unless I reinstall the OS. The contacted support and all they said was the port was being blocked even thought I added the ports to the ip tables. Anyone have any idea what would cause this? Or have a suggestion of a linux with a GUI? Weird thing is it worked fine and now it doesn't want to work >.<

 

 

~SmaTTeR

[GoNode5]

Did you save the ip tables? if you didn't save them and you reboot the vps it resets. 

[SmaTTeR]

[code]sudo service iptables save[/code]

I ran that exact command before restarting the vps so it should of saved them

 

EDIT: Now I'm using Debian and when I try and click on OSbot jar it doesn't doing anything, even it I right click and click open with java.

Edited June 14, 2016 by SmaTTeR

[Hi G00gle]

[code]sudo service iptables save[/code]

I ran that exact command before restarting the vps so it should of saved them

 

EDIT: Now I'm using Debian and when I try and click on OSbot jar it doesn't doing anything, even it I right click and click open with java.

 

 

Try running it in command line, that way it prints out a error. 

java -jar "PathToFile.jar" 

It will probably end up saying HTTPS request denied, or that it simply cannot be run because of a minor 52.0 version. This is the way to fix that: 

sudo apt-add-repository ppa:webupd8team/java

That way you add the repository to your system. After you did that, go on to the next step:

sudo apt-get update

Now you are updating the packages, and other things on your system. After that, go on to the next step.

sudo apt-get install oracle-java8-installer

This worked for me to fix the Java issue on the minor 52.0 error. 

 

 

BEAR IN MIND, YOU ARE DOWNLOADING THE PACKAGE FROM A EXTERNAL PLACE, BE AWARE THAT IF YOU GO ON, SOME PACKAGES MIGHT BE CORRUPT.

 

I, however, did it this way on my VPS, and it worked just fine.

Edited June 16, 2016 by Hi G00gle

[SmaTTeR]

Try running it in command line, that way it prints out a error. 

java -jar "PathToFile.jar" 

It will probably end up saying HTTPS request denied, or that it simply cannot be run because of a minor 52.0 version. This is the way to fix that: 

sudo apt-add-repository ppa:webupd8team/java

That way you add the repository to your system. After you did that, go on to the next step:

sudo apt-get update

Now you are updating the packages, and other things on your system. After that, go on to the next step.

sudo apt-get install oracle-java8-installer

This worked for me to fix the Java issue on the minor 52.0 error. 

 

 

BEAR IN MIND, YOU ARE DOWNLOADING THE PACKAGE FROM A EXTERNAL PLACE, BE AWARE THAT IF YOU GO ON, SOME PACKAGES MIGHT BE CORRUPT.

 

I, however, did it this way on my VPS, and it worked just fine.

Gonna try that to fix java but my main problem right now is I can't even connect to vps after a restart with vnc or putty for some reason. And the company will just say they did a nmap scan and the port is open....

[Hi G00gle]

Gonna try that to fix java but my main problem right now is I can't even connect to vps after a restart with vnc or putty for some reason. And the company will just say they did a nmap scan and the port is open....

 

I'm very sorry for not reading correctly. Does the company have their own way to login to their VPS? (Not PuTTy or VNC)

[SmaTTeR]

This is the error when I try to run the Osbot jar file.

 

java -jar "OSBot 2.4.69.jar"
Exception in thread "main" java.lang.ExceptionInInitializerError
        at org.pushingpixels.substance.internal.contrib.jgoodies.looks.common.ShadowPopupFactory.install(ShadowPopupFactory.java:115)
        at org.pushingpixels.substance.api.SubstanceLookAndFeel.initialize(SubstanceLookAndFeel.java:1781)
        at javax.swing.UIManager.setLookAndFeel(UIManager.java:538)
        at org.pushingpixels.substance.api.SubstanceLookAndFeel.setSkin(SubstanceLookAndFeel.java:2163)
        at org.pushingpixels.substance.api.SubstanceLookAndFeel.access$000(SubstanceLookAndFeel.java:92)
        at org.pushingpixels.substance.api.SubstanceLookAndFeel$3.run(SubstanceLookAndFeel.java:2136)
        at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:301)
        at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
        at java.awt.EventQueue.access$500(EventQueue.java:97)
        at java.awt.EventQueue$3.run(EventQueue.java:709)
        at java.awt.EventQueue$3.run(EventQueue.java:703)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
        at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
        at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
Caused by: java.awt.HeadlessException:
No X11 DISPLAY variable was set, but this program performed an operation which requires it.
        at sun.awt.HeadlessToolkit.getScreenResolution(HeadlessToolkit.java:226)
        at org.pushingpixels.lafwidget.utils.LookUtils.isLowResolution(LookUtils.java:435)
        at org.pushingpixels.lafwidget.utils.LookUtils.<clinit>(LookUtils.java:233)
        ... 20 more

[Hi G00gle]

 

This is the error when I try to run the Osbot jar file.

java -jar "OSBot 2.4.69.jar"
Exception in thread "main" java.lang.ExceptionInInitializerError
        at org.pushingpixels.substance.internal.contrib.jgoodies.looks.common.ShadowPopupFactory.install(ShadowPopupFactory.java:115)
        at org.pushingpixels.substance.api.SubstanceLookAndFeel.initialize(SubstanceLookAndFeel.java:1781)
        at javax.swing.UIManager.setLookAndFeel(UIManager.java:538)
        at org.pushingpixels.substance.api.SubstanceLookAndFeel.setSkin(SubstanceLookAndFeel.java:2163)
        at org.pushingpixels.substance.api.SubstanceLookAndFeel.access$000(SubstanceLookAndFeel.java:92)
        at org.pushingpixels.substance.api.SubstanceLookAndFeel$3.run(SubstanceLookAndFeel.java:2136)
        at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:301)
        at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
        at java.awt.EventQueue.access$500(EventQueue.java:97)
        at java.awt.EventQueue$3.run(EventQueue.java:709)
        at java.awt.EventQueue$3.run(EventQueue.java:703)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
        at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
        at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
Caused by: java.awt.HeadlessException:
No X11 DISPLAY variable was set, but this program performed an operation which requires it.
        at sun.awt.HeadlessToolkit.getScreenResolution(HeadlessToolkit.java:226)
        at org.pushingpixels.lafwidget.utils.LookUtils.isLowResolution(LookUtils.java:435)
        at org.pushingpixels.lafwidget.utils.LookUtils.<clinit>(LookUtils.java:233)
        ... 20 more

 

I think the problem is easy to fix with performing the following tasks:

export DISPLAY=:0.0

Or

setenv DISPLAY :0.0

The problem should be fixed by now. Last question: Do you have a GUI?

 

 

- Some documentation about your problem (This has been taken from Stackoverflow):

 

READ THIS FIRST BEFORE PERFORMING OR MAKING ANY CHANGES:

 

If you're coming in from another machine, and you're at the main display of that machine and it's running X, then you can use "ssh -X hostname" to connect to that host, and ssh will forward the X display back. ssh will also make sure that the DISPLAY environment variable is set correctly (providing it isn't being messed with in the various dot files I mentioned above). In a "ssh -X" session, the DISPLAY environment variable will have a value like "localhost:11.0", which will point to the socket that ssh is tunnelling to your local box.

 

Read http://stackoverflow.com/questions/662421/no-x11-display-variable-what-does-it-mean < here for more information about your problem (probably).

Edited June 27, 2016 by Hi G00gle