I have installed Jenkins Continues Integration system on my windows server successfully and it works without any errors. But I was unable to get Jenkins URL working with my host domain. The default Jenkins address which is http://localhost:8080 works well. My domain/server name is projectdev so I want to give Jenkins the http://projectdev/jenkins URL so that other developers in my network will be able to access Jenkins dashboard easily.
Although I added http://projectdev/jenkins as the Jenkins URL from the Jenkins configuration sections, it doesn’t work. I can’t access it from other computers in my network. But when I use http://localhost:8080 I can access the dashboard directly.
I also tried to add Jenkins as a web application on IIS and give it the address I want. But I don’t know what to provide as the physical path of Jenkins as it was installed using Jenkins.jar file.
It would be really great if someone can help me to get this done as I want.
Thank you.
You have to configure IIS to re-route requests to {domain}/jenkins to {domain}:8080/jenkins
check the info on:
http://www.iis.net/learn/web-hosting/microsoft-web-farm-framework-20-for-iis-7/setting-up-a-server-farm-with-the-web-farm-framework-20-for-iis
Try this address: http://projectdev:8080/jenkins If you type without 8080 port , the port will be 80 by default.
Related
I am newer to IIS so please forgive my ignorance. Here is my situation. I have a backend server that resides on ip xx.xx.xx.175 from here I have all my code and IIS installed here. I created a website and can access it just fine using localhost:3000. When I go to the frontend server which resides at xx.xx.xx.174 I cannot connect to the site using the URL.
I have updated the bindings, I have updated the firewall rules, I have also used netsh http add iplisten and I still cannot connect to the site. I am not sure where else to go from here as all of my Google searching lead me to the same things.
Please make sure you have added the ip address in the host file:
Open your text editor in Administrator mode.
In the text editor, open C:\Windows\System32\drivers\etc\hosts.
Add the IP Address and hostname. Example: 192.10.10.5 testserver.com.
Save the changes.
Currently I'm getting a 422 The change you requested was rejected error when trying to login to gitlab.
The only thing I changed was to follow the official doc on how to setup gitlab behind a reverse proxy. The funny thing is, if I access gitlab from the outside via https, it works perfectly and to login is possible. But accessing the gitlab instance via the internal lan directly, the above error gets thrown.
Do I miss some configuration for the nginx when http gets used?
Try first and check if your proxy is used when your are using the internal lan.
I usually set
no_proxy='localhost,.company.com'
That will avoid using the proxy for intranet access.
I have published my website in IIS. The url is http://localhost/MyDemo. I want to give this url for testing to other people (anyone). How can I do that?
I tried to give sharing permission to "Everyone" in the Edit Permission.
Please help.
There are standard port forwarding tools that allow you to do this.
A helpful link here - https://www.sitepoint.com/accessing-localhost-from-anywhere/
Now ngRok is a tool I have used many a times. Its usage is pretty straightforward.
It can be downloaded from here - https://ngrok.com/download
Once ngRok is downloaded, you have to open the ngrok.exe, and it opens a console window.
Execute the following command
ngrok http 4983 -host-header="localhost:4983"
Here 4983 is a port number, in case you have one.
Once the command is executed the tool opens up a Url, which is accessible from anywhere. The below image is your Url, and it will be valid for a certain duration of time (if you are using the tool for free).
I got an Amazon ec2 server and when I go to the URL (Public DNS (IPv4)) in my browser I get "ERR_CONNECTION_TIMED_OUT"
I did the tutorial "Installing a LAMP Web Server on Amazon Linux" http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/install-LAMP.html
But got stuck on "If you are unable to see the Apache test page, check that the security group you are using contains a rule to allow HTTP (port 80) traffic."
I checked the security groups and they both set to "All traffic
All
All
sg-7496280c (default)"
And I still can't see the test page. I've also tried using the public IP address and I get the same thing.
There were no errors when installing packages.
I am able to connect using winSCP and upload html files but it doesn't serve them.
I don't know if I'm doing the right tutorial, or if I need to do other things first, or which tutorials apply to which types of servers or if ec2 and aws are the same thing or not etc.
I tried contacting support but it said I don't get technical support for basic accounts. I tried posting this on Amazon forums but it said something like "you can't post new threads right now, try again later"
I'm only doing any of this because you can't run node.js on hostgator.
ERR_CONNECTION_TIMED_OUT only happen either your apache not running or your server or your server is redirecting too much
Just I am unsure where you uploaded your HTML file and with what permission.
Do the basic thing reinstall only apache first.
check in your inbound and outbound port in aws security group in aws dashboard
if 80 port is open with anywhere option
check for
security rule
See if apache default page come. then upload your file.
can you tell in what directory you uploaded all your HTML
"ERR_CONNECTION_TIMED_OUT" can also be happen if you have not properly configure security group while creating the EC2 instance as it allows specific traffic to reach your instance.
If you want to set up a web server and allow Internet traffic to reach your instance, add rules that allow unrestricted access to the HTTP and HTTPS ports.
and copy Public IPV4 and use to visit the webpage rather than copying the url.
yesterday I installed gitlab on a vm of mine and configured everything to work with it.
Gitlab listens on port 8081 of my domain (e.g. domain:8081).
I have an apache instance which listens to port 80 and 443, so I did a forward there (e.g. domain/git).
Everything worked fine (except the css theme of domain/git, but thats no problem), but then I changed the root url (I think, I don't know how this settings is called) in the admin section directly in gitlab to http://domain/git to let gitlab show me directly this url if I want to copy a URL to clone.
Now I can't access my gitlab instance, because I do have an redirection loop.
I also can't find where the setting was done by gitlab itself, I guess it's stored in the database and not any file.
Can someone help me figure out how to change this particular configuration back to default?
Thanks in advance!
You likely changed the 'homepage url' used for redirecting logged out users. Instead of hitting the domain mainpage, hit /users/sign_in and you should be able to sign back in as your admin user. Go to the admin section, and clear out the setting.
You instead need to go into your config/gitlab.yml (source install) or /etc/gitlab/gitlab.rb (package install) and set the external_url to be the address you wanted.
Then restart/reconfigure the app to have it used in the git clone instructions.