# Noob ingress question

**URL:** https://forums.suse.com/t/noob-ingress-question/14647
**Category:** SUSE Rancher Prime
**Created:** [June 26, 2019, 4:57pm UTC](https://forums.suse.com/t/noob-ingress-question/14647 "2019-06-26T16:57:42Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![bogdanbrudiu](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/bogdanbrudiu/32/6198_2.png) [@bogdanbrudiu](https://forums.suse.com/u/bogdanbrudiu)
#### Post date: [June 26, 2019, 4:57pm UTC](https://forums.suse.com/t/noob-ingress-question/14647/1 "2019-06-26T16:57:42Z")

</div>

I have on the same VPS started rancher:rancher (on 8443 & 8080) and rancher:agent (on 443 & 80). I am able to access the dashboard using mydomain:8443  
I would like to be able to access it with rancher.mydomain:443 but I cannot figure out how…

I have tried creating a service named dashboard with  
Resolves To: An external hostname  
Target Hostname: mydomain  
Publish the service port 8443 to Target Port 443

and Ingress rule with  
Request Host: rancher.mydomain  
Target the service dashboard and port 443

I had no success and assume is because of the https certificates and tried again a similar scenario with hello-world workload.  
I deployed the hello world and created a ingress entry for test.mydomain that works OK and I am able to access it.  
Then I created a new service named copy that points to test.mydomain port 80 and an ingress rule for testcopy.mydomain with service copy and no success…

Certainly I am not using this how I should… How to do this?

---

<div class="post-metadata">

### Author: ![bogdanbrudiu](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/bogdanbrudiu/32/6198_2.png) [@bogdanbrudiu](https://forums.suse.com/u/bogdanbrudiu)
#### Post date: [June 27, 2019, 6:16am UTC](https://forums.suse.com/t/noob-ingress-question/14647/2 "2019-06-27T06:16:04Z")

</div>

Similar with [How to expose Rancher UI on the Internet using Rancher Ingress?](http://forums.suse.com/t/how-to-expose-rancher-ui-on-the-internet-using-rancher-ingress/14561) but still no solution…

---

<div class="post-metadata">

### Author: ![bogdanbrudiu](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/bogdanbrudiu/32/6198_2.png) [@bogdanbrudiu](https://forums.suse.com/u/bogdanbrudiu)
#### Post date: [June 27, 2019, 8:12am UTC](https://forums.suse.com/t/noob-ingress-question/14647/3 "2019-06-27T08:12:34Z")

</div>

Similar with [Ingress to Rancher Server Itself](http://forums.suse.com/t/ingress-to-rancher-server-itself/13707)

---

<div class="post-metadata">

### Author: ![bogdanbrudiu](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/bogdanbrudiu/32/6198_2.png) [@bogdanbrudiu](https://forums.suse.com/u/bogdanbrudiu)
#### Post date: [July 10, 2019, 6:28pm UTC](https://forums.suse.com/t/noob-ingress-question/14647/4 "2019-07-10T18:28:42Z")

</div>

> [@bogdanbrudiu](#):
>
> I deployed the hello world and created a ingress entry for test.mydomain that works OK and I am able to access it.  
> Then I created a new service named copy that points to test.mydomain port 80 and an ingress rule for testcopy.mydomain with service copy and no success…

I found the solution for my hello world, for ingress I have added an annotation:

[nginx.ingress.kubernetes.io/upstream-vhost:](http://nginx.ingress.kubernetes.io/upstream-vhost:) test.mydomain

this solved the test.mydomain/testcopy.mydomain but he solution does not seam to work for rancher.mydomain
