So,
I used to install puppet module via http://forge.puppetlabs.com without any issues. But then all of a sudden I am getting an error 301 Moved Permanently when trying to install any modules.
I would run the following command
puppet module install --module_repository http://forge.puppetlabs.com puppetlabs-dism
Now this appears to fail.
I have used both 3.4.2 and 3.8.7 (updated thinking their was an issue with the version)
I also have a similar command for ubuntu which works fine, but this is without the module_repository parameter.
The reason for the --module_repository flag is to get around the ssl certificate issue not being valid.
So the question being, has this functionality been removed, or does anyone know how to get the ssl certificate to be valid.
The url is in the process of being changed to https://forge.puppet.com as explained in ticket FORGE-327. Try using the updated url and see if that works for you.
As for the ssl error, see the documentation here and look at the first bullet point. It describes the reason this is happening and solutions for it.
Related
I keep totally failing to update an etherpad-lite server. The problem: Even a Google search for the update procedure brings up hardly any information, only that one should run "git pull origin".
I have now tried this in many different ways. The update usually works, but afterwards one of these errors occurs:
Plugins can no longer be installed
The service can no longer be started (TypeError: log4js.replaceConsole is not a function)
The entire admin panel no longer works.
I tried uninstalling or updating all plug-ins before, but both hardly brought any improvements, only other errors. The update of the plugins in the admin console fails, I tried it via the updatePlugins.sh script. Here a message appears that at least etherpad-lite 1.8,6 must be installed. I am currently at version 1.8.4 and would like to update to the latest version 1.8.12. However, some of the plug-ins are still updated. A very strange behaviour.
I would be happy if someone could tell me how to properly update the etherpad-lite instance step by step. (ubuntu 20)
Thank you!
I have recently updated Etherpad-lite from version 1.8.6 to 1.8.13.
For me, executing git pull origin and then checking out the 1.8.13 release tag, with git checkout 1.8.13, made the work.
It is important, despite having Etherpad configured as a service, to run it for the first time using:
src/bin/run.sh.
Node v12.22.1
npm 6.14.12
Ubuntu 20.04.2
I hope it has been useful to you.
Having an issue with Plesk and nodejs-extension using phusion passenger.
My Plesk Version: Plesk Obsidian 18.0.31 Update #2
My OS: Ubuntu 18.04.5 LTS
Using nodejs 12.4.0 which is primarly installed via plesk.
I set up two domains. On both i run npm install via the plesk ui. Everything works and nothing results in an error, until I head to the domains, I got following error messages within development mode:
On domain 1:
Domain 1 error
On domain 2
Domain 2 error
Its a bit confusing since everything seems to work fine.
I have already tried to set an Environment variable in /etc/nginx/conf.d/phusion-passenger.conf:
passenger_env_var NODE_PATH /usr/share/passenger/node;
Reason is that in phusion passengers github somebody recommends this within an issue. And in /usr/share/passenger/node/phusion-passenger/ I found the line_reader.js.
But this doesn't solve the problem.
Thanks for helping me out
So I figured out, that the path-variables aren't correct for phusion to work. After editing them hard in the code everything works fine.
I am still not happy about this solution. So if anyone knows another option to solve this. please suggest.
I tried this framework called Frontity. For the first try (run) everything was good, I had my demo page, and it worked well. I follow these instructions.
For the second compile I got these error, and a lot: There are multiple modules with names that only differ in casing.
Only change what I have done was this one (connecting my frontity to my WordPress): https://docs.frontity.org/getting-started/connecting-to-wordpress
(Again: for the first run, it was good.)
Nothing, literally nothing was changed, I do not even started any other software :)
After all this, I deleted everything, moved to another folder, started over the whole thing and for now I only get the same errors, and an Internal Server Error in my browser.
I have this issue with or without running the xampp server.
Any idea what went wrong?
Localhost WordPress (xampp), localhost:3000 Frontity (default), Windows 10, Chrome browser.
errors after compile
Your problem is here in the console output:
I'm not sure at which point those files with differing cases are
generated, but I think the following should fix your issue:
https://stackoverflow.com/a/53901224/2638310
Ensure that the path you used in your terminal has the correct
capitalization. For example if you're using git bash on Windows and
your project has the following path:
C:\MyProjects\project-X
If you access it using cd /c/myprojects/project-x (note the lack of
capital cases) and then run npm start you might face this problem.
The solution would be to consider the project path case-sensitive and
use it as follows:
cd /C/MyProjects/project-X
I'm trying to install CentOS7 using a kickstart file with a VM. I am using a netinstall version of the ISO.
When I try to put the URL in the kickstart file, it will take a long time to check the installation source, and then fail.
I have checked the ISO, installing successfully without kickstart and using this address for the source:
url --url="http://sunsite.rediris.es/mirror/CentOS/7/os/x86_64/"
However, when using kickstart file, I install and then fail with below error message -
Error setting up base repository
Even if I manually type it in after it errors out.
Does anyone have any ideas? I have reduced my kickstart file to just that one line and it still shows the same behaviour. I don't have this problem with kickstart using the minimal or full install ISO's.
I'm just learning Linux so I didn't realize you could switch into another screen and monitor the install/run commands simultaneously.
After doing so I realised it wouldn't resolve names.
My DNS is dead/isn't responding. Used kickstart to manually assign another DNS server to the interface. This allowed the install to resolve the url. This would explain why the install worked with the netinstall iso on its own, as it was using default settings.
Hope this helps someone.
I'm trying to get Indy to work with SSL and the IdHTTP component in Lazarus installed on Ubuntu 11. I know my code is right for the http post since if I remove the https and leave it as only http it works. So I figure it's the SSL and indy's components missing Linux libraries. For window's I was use to just including the two DLL's, libeay32.dll and ssleay32.dll and it worked fine.
But in linux it seems to be another story. The only code I have is the post code:
IdHttp1.Post('url', StringList, ReturnStreamList);
Like I said it works great without the https, but when I try SSL nothing happens at all. No error since I have try and except to catch but I'm not doing anything with the catching.
I do have OpenSSL installed, I also have the following installed through apt:
libcrypto++8
libcrypto++-dev
libssl-dev
libssl0.9.8
I went to /usr/lib and both the files libcrypto.so and libssl.so are there.
Any ideas what's missing to get SSL to work with Lazarus and Indy for IdHTTP post operations?
EDIT: Ok, after following advice below I have added the exception:
on E: EIdHTTPProtocolException do
showmessage(htp1.ResponseText);
This gives me the error Error creating SSL context.
EDIT2: I ran an strace and I have pasted the output areas where it open's the SSL libraries here:
http://pastebin.com/fL6tTSGg
This was so easy it ticks me off! ha ha
Seems I was using the wrong method for the SSL. I had to set TidSSLioHandlerSocketOpenSSL.SSLOptions.Method to sslvSSLv23, it was on sslvSSLv2.
Now everything works fine :)