If you refer to the ConfigServer Security & Firewall - csf on your server, in "Upgrade" section you should see this message:
"You are running the latest version of csf. An Upgrade button will appear here if a new version becomes available"
One of the features of this firewall is its automatic update, if a new version of the CSF firewall is available, the CSF will automatically update it to the new version.
The user sent us a CSF update report and, in the explanations for us, the error is
"Unable to connect to https://download.configserver.com, retry in 300 seconds."
which we will continue to teach you how to fix this problem.
Note: This training is tested on the operating system centos 6.7
This error is due to the non-installation of Crypt-SSLeay on the server, so you must have access to the server management, you can use the putty software to log onto your ssh server and install yum by this package. After entering ssh, enter the following command on the server:
# yum install perl-Crypt-SSLeay
Wait for 5 minutes and try again if your problem still exists,
in "csf - ConfigServer Firewall" Section,click on "Firewall Configuration" buttom, then find "URLGET" and set it to "2", go to end of the page and click on "Change" buttom,then restart CSF.
If you see this Warning:
"URLGET set to use LWP but perl module is not installed"
This problem is due to the fact that Perl's required modules are not installed on the server. Some CSF firewall operations depend on the modules and packages installed in the CSF, which does not work properly if these CSF modules or packages are not installed. To fix this error, you must install perl-libwww-perl packages and net-tools and perl-LWP-protocol-https on your Linux operating system. To install these packages, you must connect to the SSH server, then log in to the server administration and enter the following command:
# yum install perl-libwww-perl net-tools perl-LWP-Protocol-https
Your Problem Solved. Good luck :)
for update CSF on Command line use:
# csf -u
I had the same problem upgrading to CSF version 13.05! The problem that I have found was the Country Block did not take note but I guess the update server is located in NL? Remove all country block restart CSF and do the
# csf -u using shell
et voilà!
Related
I have spent hours trying to fix this problem on my own but am getting nowhere and can't seem to see any other questions/solutions regarding my specific problem.
I successfully installed nodist via chocalatey via Powershell admin.
I used the following script in attempting to install the Squarespace development server per Squarespace documentation:
npm install -g #squarespace/server -y
Please noted I added the -y parameter to for yes to accept license agreement but previously didn't add this parameter but still received same result.
When trying to install the local Squarespace development server via Powershell admin, the script keeps getting hung up at the following:
Using this software requires accepting the Squarespace Developer Terms
of Use and Oracle Binary Code License Agreement . See LICENSE.txt.
The following is a screenshot of all the scripts that ran beginning from my install script:
I have done everything from reinstalling nodist several times to rebooting machine and everything else to troubleshoot.
Please note that I have also waited for more than an hour to see if the script fully executes but remains hung at the above noted line.
Why is this happening and how can I fix this?
Regards.
I launched an Ubuntu 18.04 VM with Azure. I installed a bunch of stuff that I need. Then, I used the dashboard to create a custom image from this machine. After that, I checked that the image was okay by launching some machines with that image. Everything seemed to be working fine.
Today, I launched a new instance with my custom image. Then I tried to install a few things with apt-get install and I get the following error (e.g. for unzip):
sudo: unable to resolve host ABCDEFG: Resource temporarily unavailable
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package unzip is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'unzip' has no installation candidate
This same thing happens for any package I try to install. After testing some basic things with my repositories, I checked the internet connection with ping. E.g. ping www.google.com which is also not working. I launched a vanilla Ubuntu 18.04 instance and I am not having these problems with that machine.
I have also tried sudo reboot but no luck with that. I did notice that when the system booted it shows the following error, also indicating that something is wrong with the internet:
Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check your Internet connection or proxy settings
Any help is greatly appreciated.
So, after some digging around, I found this answer to something similar: https://askubuntu.com/questions/1045278/ubuntu-server-18-04-temporary-failure-in-name-resolution.
I used the following command and the internet started working again:
sudo ln -s ../run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
This is a little different than the answer on askubuntu because this is on an Azure image. First, I noticed that my image was missing resolv.conf in /etc. Using ls -la /etc/resolv.conf on a different azure image, I saw that it was a symbolic link to ../run/systemd/resolve/stub-resolve.conf, so I created a link that matched this format on my machine and that fixed things.
** EDIT **
It's worth noting that when you deprovision the VM to create the custom image, it does say:
WARNING! The waagent service will be stopped.
WARNING! Cached DHCP leases will be deleted.
WARNING! root password will be disabled. You will not be able to login as root.
WARNING! /etc/resolv.conf will be deleted.
WARNING! xxxx account and entire home directory will be deleted.
I've got a Win 10 box with Cygwin and the X packages installed. I run xlaunch and start up the X server. I then do "ssh -Y user#myserver". Then I su and run virt-manager. I get an error:
Cygwin: Unable to initialize GTK: could not open display
echo $DISPLAY shows:
localhost:10.0
I've tried changing it with EXPORT DISPLAY=localhost:0.0 with no luck.
I've googled and read all of the similar questions but none address my problem, as simple as I'm sure it is.
Starting from xorg-server version 1.17 , the option -nolisten tcp is now the default, so the server only accepts local connections on a unix domain socket.
To allow connection by TCP you should use the option -listen that has been added to restore the previous behaviour.
As reported by the package maintainer:
https://sourceware.org/ml/cygwin-announce/2015-10/msg00111.html
I have a Linux server that is running Debian squeeze, I can not run apt-get update on it. I get errors like these:
W: Failed to fetch http://ftp.us.debian.org/debian/dists/squeeze/main/binary-i386/Packages.gz
Unable to connect to 10.197.3.5:3142:
I can successfully ping ftp.us.debian.org ,but the ip address that it shows is different than the ip address shown with the unable to connect message.
I assumed this was an issue with DNS translation, so I changed my DNS server to google's 8.8.8.8 server
Running dig google.com
shows that the DNS server is in fact the google server I specified.
I'm stumped. It may be of note that I am forwarding port 22 and port 80 to my router so my teammates can ssh and view the webpage associated with this server. I don't think this is the issue since this occurs even when I stop the forwarding.
Turns out the original holder of this server set up a proxy in /etc/apt/apt.conf that wasn't working, (I don't know why this was)
I remove this line form that file
Acquire::http::Proxy "PROXYIP/apt-cacher/";
I have fixed similar issue applying one comment about your issue:
My environment is:
Linux debianlpi 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1 (2016-12-30) x86_64 GNU/Linux
The issue that I got, was:
root#debianlpi:~# apt-get install vim
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
vim-runtime
Suggested packages:
ctags vim-doc vim-scripts
The following NEW packages will be installed:
vim vim-runtime
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 5,999 kB of archives.
After this operation, 28.5 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
WARNING: The following packages cannot be authenticated!
vim-runtime vim
Install these packages without verification? [y/N] y
0% [Connecting to idcproxy.compabc.com (432.1.2.20)]
It was fixed removing line in /etc/apt/apt.conf:
root#debianlpi:~# cat /etc/apt/apt.conf
#Acquire::http::Proxy "http://idcproxy.compabc.com:80";
When I execute this command below:
scp -P 36000 hdfs#192.168.0.114:~/tmp.txt SOQ_log.txt
I get an error:
command-line: line 0: Bad configuration option: PermitLocalCommand
Does anyone know why?
scp runs a copy of the ssh program to create the communications channel, and it runs ssh with the options:
-oForwardAgent=no -oPermitLocalCommand=no -oClearAllForwardings=yes
So that explains where the "PermitLocalCommand" option is coming from in the first place. I'll add that sftp uses the same options to run ssh, so it'll probably display the same behavior.
"PermitLocalCommand" is normally a valid ssh configuration option. If your copy of ssh is complaining about it, then it seems that your copy of ssh isn't the normal copy of ssh that goes with your copy of scp.
This serverfault question suggests that the error could be due to someone installing a malware version of ssh (ie, a rootkit) on your system. This forum thread also suggests that the problem is due to having an altered version of ssh, which was fixed by removing and reinstalling the OpenSSH client utilities.
An alternate explanation would be that someone--maybe your Linux distro maintainer--has installed a version of ssh on your system with that option removed, and you're using it unawares. Or you have a very old version of the ssh program for some reason, which doesn't support the option.
My system is CentOs 5.9
I'm facing the same problem, I found it to be due to this configuration line in /etc/ssh/sshd_config:
# override default of no subsystems
Subsystem sftp /opt/libexec/sftp-server
But I cannot run /opt/libexec/sftp-server, it is broken for some reason
now it is solved by reinstall the remote openssh-server:
yum erase openssh-server
yum install openssh-server
now the changes to
# override default of no subsystems
Subsystem sftp /usr/libexec/openssh/sftp-server
and /usr/libexec/openssh/sftp-server is runnable
don't forget to execute:
/etc/init.d/sshd restart
Sometimes command cannot parse this kind of stuff
:~/
Id change it to the full path.