Linux jenkins nginx move to location

Деректива Nginx — location с примерами

Директива location служит для установки конфигурации в зависимости от URI-запроса. Синтаксис location в общем виде следующий:

Перед тем, как перейти к более детальному изучению, нужно заметить, что location определяется в контексте server (или в location в случае вложенной директивы), и в одном настраиваемом виртуальном хосте могут использоваться разные конфигурации в зависимости от обрабатываемого сервером URI.

Префикс «@» («собака») определяет именованные расположения. Такие location’ы не используются для обработки обычных запросов. Вместо этого они используются для перенаправления запросов (пример №6). Они не могут быть вложенными и содержать в себе вложенные.

1. = Строковые совпадения. Если найдено, проверка заканчивается. = значит полное совпадение шаблона и проверяемой строки, например = / — заход в секцию будет исключительно для корня, и даже файлы в корне уже сюда не подходят.
2. ^

Приоритетное строковое значение. Хотя по-моему было бы правильнее назвать «приоритетным регулярным выражением», поскольку в отличии от = требуется совпадение только начала. ^

/ полностью отключит регулярные выражения для секции server, если нет более точного location без ^

* Регулярные выражения, в порядке определения в конфиге. При совпадении — выполняется этот регэксп, проверка заканчивается.

— с учётом регистра,

* — без.

Если не было найдено подходящей регулярки, используется наибольшее совпадение из п.3.

Источник

Reverse proxy — Nginx

In situations where you have existing web sites on your server, you may find it useful to run Jenkins (or the servlet container that Jenkins runs in) behind Nginx, so that you can bind Jenkins to the part of a bigger website that you may have. This section discusses some of the approaches for doing this.

When a request arrives for certain URLs, Nginx becomes a proxy and further forward that request to Jenkins, then it forwards the response back to the client. A typical set up for mod_proxy would look like this:

This assumes that you run Jenkins on port 8080. Remember to create the folder /var/log/nginx/jenkins.

For this set up to work, the context path of Jenkins must be the same between your Nginx and Jenkins (that is, you can’t run Jenkins on http://localhost:8081/ci and have it exposed at http://localhost:80/jenkins).

Set the context path by modifying the jenkins.xml configuration file and adding —prefix=/jenkins to the entry.

If you are having problems with some paths (eg folders) with Blue Ocean, you may need to add the following snippet to your proxy configuration:

To give Nginx permission to read Jenkins web root folder, add the nginx user to the Jenkins group:

If the last command failed because the nginx user is not defined in the system, then you can try adding the www-data user to the Jenkins group:

If you are experiencing timeouts when attempting to run long CLI commands through a proxy in Jenkins, you can increase the proxy_read_timeout setting as necessary. Older versions of Jenkins may not respect the proxy_read_timeout setting.

If you are experiencing the following error when attempting to run long CLI commands in Jenkins and Jenkins is running behind Nginx, it is probably due to Nginx timing out the CLI connection. You can increase the proxy_read_timeout setting as necessary so the command will complete successfully.

Источник

How to Setup Jenkins with SSL with Nginx Reverse Proxy on Ubuntu 18.04

Since this post shares cloud strategies with awesome people like you, naturally this post may contain affiliate links for products I use and love. If you click on those links and make a purchase, I’ll earn some coffee money which I promise to drink while creating more helpful content like this.

How to Setup Jenkins with SSL with Nginx Reverse Proxy on Ubuntu 18.04. By default Jenkins listens on port 8080 with it’s in-built web server. But it is necessary to secure Jenkins with SSL for protecting the sensitive data.

In this tutorial you are going to learn how to setup Nginx as a reverse proxy to Jenkins on Ubuntu 18.04 on Google Cloud.

This setup is tested on Google Cloud and it will run the same on any Linux distributions.

Best Hosting for your Business

Platform	Reviews	Pricing
Cloudways	★★★★★	$10
Kinsta – Google Cloud	★★★★★	$30

Prerequisites

• A running Compute Engine, see the Setting up Compute Engine Instance with Ubuntu 18.04
• Initial Ubuntu Server Set up.
• Jenkins installed with the steps listed on How to install Jenkins on Ubuntu 18.04
• DNS setup with the steps listed in Setting up Google Cloud DNS for your domain

Install Nginx

Install Nginx with the following command.

This command will install Nginx on your VM instance.

Setup Firewall

Once Nginx is installed you can configure firewall, Nginx registers itself with ufw . So, you can allow the necessary ports and enable ufw.

Make sure you have added rules for SSH port 22, if you haven’t done this you cannot access the SSH. Once you have verified you can enable UFW.

Configure Nginx for Jenkins

Now it’s time to configure Nginx as a reverse proxy for Jenkins on a subdomain.

Remove the default Nginx configuration.

Create a new configuration for Jenkins

Configuration for Jenkins on Subdomain

Paste this new configuration setting and hit Ctrl+X followed by Y to save the file.

Configuration for Jenkins on Sub-directory

Paste this new configuration setting and hit Ctrl+X followed by Y to save the file.

Hit Ctrl + X followed by Y and Enter to save and exit the file.

Enable the configuration.

Configure Jenkins for Nginx

In order to Jenkins work with Nignx you need to make Jenkins to listen on localhost

Find the JENKINS_ARGS line and add —httpListenAddress=127.0.0.1 to the existing arguments.

So, the line will look similar to the one below.

For sub-directory configuration you need to add additional argument with the directory name with —prefix

Save and exit the file. Finally restart Jenkins.

Check the configuration and restart Nginx.

Now Nginx is setup as a reverse proxy for Jenkins.

Install Free Let’s Encrypt SSL Certificate

HTTPS
HTTPS is a protocol for secure communication between a server (instance) and a client (web browser). Due to the introduction of Let’s Encrypt, which provides free SSL certificates, HTTPS are adopted by everyone and also provides trust to your audiences.

Now we have installed Certbot by Let’s Encrypt for Ubuntu 18.04, run this command to receive your certificates.

Enter your email and agree to the terms and conditions, then you will receive the list of domains you need to generate SSL certificate.

To select all domains simply hit Enter

The Certbot client will automatically generate the new certificate for your domain. Now we need to update the Nginx config.

Configure SSL

Once the SSL is installed, you can configure it in your Nginx file.

Hit CTRL+X followed by Y to save the changes.

Check your configuration and restart Nginx for the changes to take effect.

Renewing SSL Certificate

Certificates provided by Let’s Encrypt are valid for 90 days only, so you need to renew them often. Now you set up a cronjob to check for the certificate which is due to expire in next 30 days and renew it automatically.

Add this line at the end of the file

Hit CTRL+X followed by Y to save the changes.

This cronjob will attempt to check for renewing the certificate twice daily.

That’s all now you can visit your domain name in your web browser. you can see your Jenkins login page with HTTPS.

Conclusion

In this tutorial you have installed Nginx, configured UFW, setup new reverse proxy configuration for Jenkins and installed SSL and configured Jenkins for Nginx.

Cloudbooklet builds a large collection of Linux based guides and tutorials on Cloud platforms like Google Cloud, AWS, Azure, DigitalOcean and more

Источник

gonzaloplaza / aws_ec2_nginx_jenkins_installation.md

Jenkins Installation through NGINX proxy — Ubuntu 16.04 on AWS EC2 (custom tld subdomain)

The following guide includes all steps needed to install a Jenkins Server on AWS EC2 (Ubuntu 16.04 LTS), using NGINX as proxy with custom tld

1. Set up EC2 instance

• Selected type: t2.micro (1GB) (for this example, you can choose any type)
• AMI: Ubuntu 16.04 LTD 64bits (AWS AMI repository)
• 20GB SSD storage
• Security Group: Opened (inbound) for web ports: 80, 443 and 22
• Set up userdata script (below): This will update system and install: JRE8, Docker, Jenkins and NGINX

Connect it via ssh to check all scripts/packages were successfully installed. You can enter your public ip address or public dns name for instance to see nginx default page on port 80. If userdata script didn’t work for any reason, you can execute these commands manually via SSH on your EC2 instance (Order is important)

1. Assign your tls domain or subdomain to instance ipv4 address.

1. Configure nginx proxy for Jenkins

Via ssh remove default virtual host /etc/nginx/sites-available/default and create new one

Include the following configuration replacing your subdomain

Note: : Due to nginx error with logs, we create manually these files and assign them jenkins user:

And then we check nignx configuration BEFORE reload server:

If everything is fine, we must reload/restart our nginx server:

1. Access Jenkins via subdomain

If you see Jenkins first installation screen, looks like everything is working fine!

1. Enter default Jenkins password and create admin user

Default password for Jenkins is located (plain text) on our server. Access via SSH and copy it:

Enter it inside your Jenkins installation wizard and continue creating your user.

Источник

How to place Jenkins behind Nginx

The Nginx server is running HTTPS linked to the domain www.example.com . The Jenkins is running on the same server on a port 8080. I have successfully configured Nginx to route all unsecured traffic from port 80 to the secured one via port 443 using Nginx config location statement:

Now, typing www.example.com into the web browser connects me to Jenkins web interface over the secured HTTPS. That’s is great. But the problem is that with the location / all the traffic to www.example.com is routed to Jenkins.

I would like to go ahead and modify the location to contain /jenkins :

Trying to load Jenkins from www.example.com/jenkins brings up an error:

To fix it, I use Nginx rewrite statement:

Now, I am able to access Jenkins at www.example.com/jenkins , but only at Jenkins root URL / . Clicking any navigation link in Jenkins web interface, brings up 404 Not Found error.

Again, the https://www.example.com/ connects me to Jenkins root / and loads the main Jenkins web interface. Clicking Manage Jenkins button in the Jenkins web interface attempts to route to https://www.example.com/manage . It breaks with the same 404 Not Found error.

I’ve tried to use another rewrite regex that removes the word /jenkins in the URL before sending the request to http://localhost:8080 :

The navigation to the main root Jenkins site now have to be done with

(the URL must end with the forward slash / ).

It does load the main Jenkins interface. But again, all the Jenkins internal navigation links are broken.

After playing around, I have noticed, that clicking Manage Jenkins button routes to

resulting to 404 Not Found error.

If I would modify this URL to

it successfully loads the Manage Jenkins page. It seems the solution is somewhere nearby.

Is there a way to configure Jenkins routing so it inserts a custom /jenkins in to the internal URLs it creates, so clicking the Manage Jenkins button would result to

Источник