I'm trying to install an Umbraco version 8.4.0 on Windows 2016 Standard Server.
The dev machine is Windows 10 Pro on which the installation works fine.
But when I deploy to the Windows 2016 Standard Server the pages loaded do not format well - the footer, header and other compositions setup in the back-end do render.
There are no 500 server errors or Javascript errors in console. I'm clueless about whats going wrong?
Has anyone installed Umbraco v8 on windows 2016 server, are there any special considerations for installing it?
Please could someone help me, I'm really stuck on it and not sure how to go and resolve it.
We gave "Network Service" permissions to modify the website folders. That fixed it, not sure though why because Umbraco was already running without the "Network services" in the permissions. It was only the new release of the website that got affected, the previous release had no issues without Network Services having these permissions.
If anyone get stuck with something like this should check the permissions for the website folders.
I have Mirth Connect Version 2.2.3.6825 installed on RHL I want to access my Mirth my Local Machine which have Java 1.8(Java 1.7 it Work fine), I am not able to launch the Administrator tool of Mirth. When I clicked on the administrator button, It opened the window saying starting application after giving User name and Password it give error 'There was an error connecting to the server at the specified address. Please verify that the server is up and running'
http://www.mirthcorp.com/community/wiki/display/mirth/System+Requirements
Java 8 should work with version 2.2.3, but you must be using the Oracle JRE. OpenJDK only recently became supported with version 3.7.
You may also want to try using the new Administrator Launcher available on the mirth downloads page. It comes bundled with a Java 8 JVM so that you don't need to install one separately. It works with all versions of mirth from 2.x and up. See announcement here: https://www.mirthcorp.com/community/forums/showthread.php?t=218662
I have a fresh install of Jenkins 2.32.2 on Ubuntu.
Opened a browser on the instance and get to a page titled Offline, with the message "This Jenkins instance appears to be offline" and offers options to "Configure Proxy" or "Skip Plugin Installation"
The machine clearly isn't offline as I just used the internet connection to do the installation.
I also had a previous installation, done exactly the same way, that was working.
I removed the previous installation as Pipelines wouldn't work and Google told me it was because of JDK 9. So I removed all the JDK/JRE installations as well as jenkins, fresh installed JDK 8 only, installed Jenkins, and got to here.
Jenkins has worked on this box in the past so what makes it think it is offline?
Update: Found a log file /var/lib/jenkins/logs/tasks/Download metadata.log
and it starts with a message FATAL: Connection refused (Connection refused)
I would think that indicates that the internet connection is OK, but something else is stopping it getting data?
Update: Based on other research I checked the Update Site in the Plugin Manager. This is listed as http://updates.jenkins-ci.org/update-center.json and, from the command line a wget of this file succeeds. So most definitely not a connection issue. Worked with both http and https, jenkins works with neither.
In my case, it has something to do with SSL. I manage to fix it by editing /var/lib/jenkins/hudson.model.UpdateCenter.xml and change url to use http instead of https.
Restart jenkins and reload the website, it no longer shows offline.
For macOS users:
Step -1: Edit /Users/Shared/Jenkins/Home/hudson.model.UpdateCenter.xml and change url to use http instead of https.
Step -2: Restart jenkins (for instance by going to http:localhost:8080) and reload the website
Step -3(Optional): If it asks for user and password and if you don't remember creating one; default user is admin and copy the password from
sudo cat /Users/Shared/Jenkins/Home/secrets/initialAdminPassword
credits - #Alex in this post and #Tuan Pham here and #Joe Walsh for the comment on macOS directory path
There is something wrong with the internet connection of update center.I have met the same situation with Jenkins installed on macOS.
You can try to modify the hudson.model.UpdateCenter.xml file.
Jenkins installed with .pkg package on macOS,the file path is:
/Users/Shared/Jenkins/Home/hudson.model.UpdateCenter.xml
Jenkins installed by Homebrew on macOS,the file path is:
/Users/{username}/.jenkins/hudson.model.UpdateCenter.xml
Open the file:
<?xml version='1.1' encoding='UTF-8'?>
<sites>
<site>
<id>default</id>
<url>https://updates.jenkins.io/update-center.json</url>
</site>
</sites>
You can try to change https://updates.jenkins.io/update-center.json to:
http://updates.jenkins.io/update-center.json
or
// If you are in China or near China area,https and http are both OK.
https://mirrors.tuna.tsinghua.edu.cn/jenkins/updates/current/update-center.json
And then you can restart Jenkins by:
//loading the URL to restart Jenkins.
http://localhost:8080/restart
or
// Use Homebrew command to restart Jenkins if you installed Jenkins LTS version by Homebrew.
brew services restart jenkins-lts
in my case (macOS), updating jdk to 8 and reinstall jenkins solved the problem.
The issue is that for some reason Jenkins doesn't have access to the certificates chain of the Jenkins updates service.
On Ubuntu 18.04 I had this issue and the next links and instructions helped me to start Jenkins properly without modifying the default url or using a proxy of some sort.
Installing a new JDK 8(u101+) with JAVA_HOME should do the trick like at:
https://www.digitalocean.com/community/tutorials/how-to-install-java-with-apt-on-ubuntu-18-04
is making sure that Lets Encrypt certificates are installed and available on the OS/SYSTEM.
To test it you can use the instructions at:
Does Java support Let's Encrypt certificates?
And to install manually if required the Let's encrypt root chain using the next script:
https://gist.github.com/Firefishy/109b0f1a90156f6c933a50fe40aa777e
I also faced this issue i.e. This Jenkins instance appears to be offline on windows 10.
Below are the steps I followed to solve it:
Navigate to the Jenkins Home Directory.
For me, the default home directory is: C:\Windows\System32\config\systemprofile\AppData\Local\Jenkins.jenkins
Changed the protocol from HTTPS to HTTP in the file hudson.model.UpdateCenter.xml
Restarted Jenkins (Go to C:\Program Files\Jenkins and then execute jenkins.exe stop, jenkins.exe start)
Logged in to Jenkins again (http://localhost:8080/).
The offline error got solved.
In my case i have changed https to http in URL line of /var/lib/jenkins/hudson.model.UpdateCenter.xml file
and restarted the jenkins. It started functioning.
in case you are running jenkins in a container and vi is not installed
access your container in interactive mode
docker exec -it jenkins-ci /bin/bash
use this sed command to replace https with http
sed -i 's/https/http/g' /var/jenkins_home/hudson.model.UpdateCenter.xml
This mostly happens when you are working with company issued PC Windows OS.
Fix :-
click on "Configure Proxy" ask your IT team for specific server and port values that can bypass firewall and give your windows username & password. In this way you can resolve windows firewall and offline Jenkins issue.
I researched a lot over Internet but nowhere the fix is available.
Thanks!
For Ubuntu,
go to /home/username/.Jenkins/Hudson.model.UpdateCenter.xml and
edit the file from https to http.
On MacOS 10.11.6 :
Go to /Users/<UserName>/.jenkins
Open the file hudson.model.UpdateCenter.xml
Change the value of default from https://xxx to http://xxx
Took note of the secret Administrator password path that Jenkins displays when first opening http://localhost:8080/ on a browser.
The path was: C:\Users{username}\AppData\Local\Jenkins.jenkins\secrets.
Therefore the hudson.model.UpdateCenter file was at C:\Users{username}\AppData\Local\Jenkins.jenkins\
Updated the hudson.model.UpdateCenter file in notepad to have text http instead of https as follows:
http://updates.jenkins.io/update-center.json
Reloaded the http://localhost:8080/ page but still showed the text "This Jenkins instance appears to be offline."
Then navigated to the Services App in Windows (click Windows and type 'Services App' and it should display the App in the search list)
In the services App right clicked the Jenkins service and selected Restart.
After Windows restarted the Jenkins service navigated to http://localhost:8080/
The Jenkins page wouldn't even load. Navigated to the Jenkins login page: http://localhost:8080/login?from=%2F
Then got a loading page with text:'Please wait while Jenkins is getting ready to work ...
Your browser will reload automatically when Jenkins is ready.'
Assumed that Jenkins was still restarting.
Once the Jenkins login page loaded, entered that password/secret again and clicked Continue.
This time the page with "This Jenkins instance appears to be offline." was not displayed. Jenkins displayed a Getting Started -> Customize Jenkins page with buttons to install plugins.
For Windows OS,
follow below steps:
Go to C:\Users\\*your user name*\\.jenkins
Open the file hudson.model.UpdateCenter.xml
Update the value of url from https://xxx to http://xxx
I make no claims about this, especially Java related (I personally cannot stand the language), but on my Ubuntu 18.04 L/T, I needed to stand-up a standalone Jenkins instance; So I installed both the Java on which Jenkins appears to be dependent and Jenkins itself
sudo apt install openjdk-8-jdk jenkins
Then I updated the Jenkins defaults
sudo gvim /etc/default/jenkins
... inserting the following at the top of the file - only because editing /etc/init.d/jenkins appeared to serve no purpose as it had no effect whatsoever ...
JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/
PATH=$JAVA_HOME:$PATH
Finally, save & quit ... then attempt Jenkins restart
sudo service jenkins restart
HTH - it certainly worked for me :-)
I'm working on a Mac, and in my case, it turned out that the version of Java Jenkins was using (1.8.0u66) wasn't up to date enough. I had both Java 11 and Java 14 installed, but the jenkins-lts script was coded to force use of Java 8. Rather than install a more up to date JDK 8 installation, I modified the script to run ${JAVA_HOME}/bin/java and set JAVA_HOME to the JDK 11 installation.
It might not always be an option but if you have a choice use different Image. I used Debian GNU/Linux 10 and it worked like a charm.
Re-installing JAVA JDK8 worked for me.
Another possibility - make sure DNS functions properly for Jenkins.
In my case, I followed Kubernetes setup instructions here to install Jenkins, and it led to this problem.
I enabled logging on CoreDNS and saw this:
│ [INFO] 10.70.116.14:45888 - 50490 "AAAA IN updates.jenkins.io.svc.cluster.local. udp 54 false 512" NXDOMAIN qr,aa,rd 147 0.0001896s │
│ [INFO] 10.70.116.14:45888 - 32566 "A IN updates.jenkins.io.svc.cluster.local. udp 54 false 512" NXDOMAIN qr,aa,rd 147 0.000169468s │
│ [INFO] 10.70.116.14:57907 - 22912 "A IN updates.jenkins.io.localdomain. udp 48 false 512" NOERROR qr,aa 110 0.000907476s │
│ [INFO] 10.70.116.14:57907 - 52100 "AAAA IN updates.jenkins.io.localdomain. udp 48 false 512" NOERROR qr,aa 110 0.001709031s
The lookups were all cluster-local.
If I edited the URL (as suggested in other answers here) to include a dot after updates.jenkins.io. then hostname lookup worked and the URL resolved. Though Jenkins' next step errors for the same reason.
In the end I discovered the problem was ClusterFirst mode of the pod's DNS. I added dnsPolicy: Default to the deployment's pod template spec (the instructions link above), and now it works.
Even I faced similar issue, then figured out that JDK that I was using is 8 instead of 11.
Check jenkins jdk combination under jenkins official site
I used JDK11 with Jenkins 2.3031 version and it worked fine - all plugins got downloaded
In my case, I use WINDOWS OS. So, jenkins was installed in my C drive.
PATH : C:\Users\Username\ .jenkins
Under "hudson.model.UpdateCenter" file change "https" to "http"
<?xml version='1.1' encoding='UTF-8'?>
<sites>
<site>
<id>default</id>
<url>http://updates.jenkins.io/update-center.json</url>
</site>
</sites>
As some others pointed out, in Windows, this could be because of firewall restrictions set by company infrastructure.
For my case, I need the recommended plugins to be present (e.g. Folders plugin)
My workaround was:
A. Install same Jenkins version into my personal laptop/VM, and be sure to install the recommended plugins the first time you browse to the Jenkins Web Page.
B. Copy the plugins folder from my personal laptop's JENKINS HOME folder (i.e. ProgramData\Jenkins...) into the Jenkins plugins folder of the company laptop.
Total size of the plugins folder was around 150MB (zipped).
Enter this before running Jenkins.
# iptalbes -F
It may be because of the firewall.
jenkins_enable="YES"
jenkins_home="/usr/local/jenkins"
jenkins_user="jenkins"
jenkins_args="--webroot=${jenkins_home}/war --httpListenAddress=*.*.*.* --httpPort=8180"
#jenkins_java_opts="-Djavax.net.ssl.trustStore=/usr/local/jenkins/cacerts -Djava.net.preferIPv6Addresses=true"
#jenkins_java_opts="-Djavax.net.ssl.trustStore=/usr/local/jenkins/cacerts -Djava.net.preferIPv4Addresses=true"
I have a Cordova-Ionic application on Visual Studio (Microsoft Visual Studio Community 2015, Version 14.0.25123.00 Update 2). I am able to run the app on my android phone and all is good. I want to test the app by also running it on an iPhone/iOS simulator.
I have OS X El Capitan (version 10.11.6) running as a VM on virtual box. I have been following this guide (https://taco.visualstudio.com/en-us/docs/ios-guide/) to try to test the app on apple devices. I have installed version 0.12.9 Node.js and Xcode Version 8 Beta 4. I have also installed xcode command line tools, remote agent, homebrew. I have tried running 'remotebuild test' in a terminal and it executes successfully, ending with 'taco-remote test passed.' However, this is where the problems start.
To attempt to use secure remotebuild, i run 'remotebuild certificates reset' and then 'remotebuild certificates generate' in the terminal. I see
host: noyolks-iMac.local
port: 3000
PIN: 121422
I then run 'remotebuild'. On visual studios on my windows machine, I then go to tools -> options -> tools for apache cordova -> iOS configuration. I set 'Enable remote iOS processing' to 'true', 'host' to 'noyolks-iMac.local', 'port' to '3000', 'secure mode' to 'true', 'security pin' to '121422'. However, when i press ok, i see the following error popup 'Unable to connect to remote iOS build server. Underlying exception: The remote name could not be resolved: 'noyolks-imac.local''.
I try using the IP instead in place of the host name as suggested in the guide. On OS X, i go system preferences -> network. I then see '10.0.2.15' under IP address. I go back to my windows machine. I try '10.0.2.15' in place of the 'host'. When i press ok, i see the following error popup 'An error occurred trying to acquire certificate from https://10.0.2.15.'.
Please note, I ensured that all the above was done within the 10 minutes window before the security pin expires.
Following the guide, I then tried to start the remote agent without secure mode. I run 'remotebuild --secure false'. Once again on visual studio on my windows machine, i try host 'noyolks-imac.local' first (with 'port' to '3000', 'enable remote iOS processing' to 'true', 'secure mode' to 'false') and i get the error popup 'Unable to connect to remote iOS build server. Underlying exception: The remote name could not be resolved: 'noyolks-imac.local''.
Once again, running without secure mode, i instead use the ip address in place of the host '10.0.2.15'. I get the error popup 'Unable to connect to remote iOS build server. Underlying exception: Unable to connect to the remote server'.
I have also tried a similar procedure using a friends mac book pro and have not been able to get this to work. Any help would be appreciated and please do feel free to ask for any other information you might need.
Thanks.
I'm an idiot. The problem was that I couldnt even ping my El Capitan VM. Changing the network adapter settings in virtualbox to 'bridged adapter' solved this.
I have installed Jenkins(1.621) on Windows Server 2008 R2-(Enterprise),from command prompt with option java -jar jenkins.war. After installation I tried launch jenkins in google chrome browser. For couple of times I can successfully launch the jenkins, but third time I am getting the error:
Oops! Google Chrome could not connect to localhost:8080 : Jenkins Launch Error
I tried uninstalling and reinstalling the Jenkins, but same result after couple of launch. I am not able to see any logs generated in Jenkins installation directory. (C:\Users\ic003981.jenkins).
How can I solve this issue?
Installing new Google Chrome Version 45.0.2454.99 m has solved the problem of Jenkins launch error.