I noticed that if I deploy to an address like https://127.0.0.1:44309 (or https.//192.168.1.31:44309), then the port is missing in the redirect url.
I think that it may be a bug: Vendr fails to create redirect url in case it contains both numbers and port.
Any help is appreciated
Ok, I've just looked into this and yea, it does appear that we have some code that says if it's on https and you aren't on localhost it's just always setting the port to 443.
Unfortunately there isn't a code comment as to why we did that so I'm not sure why we needed that. I'll create a bug report for this and get it updated in the next release, but until then you might try using something like nip.io or ngrok to give you a temporary URL to view the site on.
Vendr continue url problem
I installed Vendr package and some payment packages like invoicing, paypal, stripe. Everything works fine if I deploy my umbraco site at local address like https://localhost:44309. But if I deploy my umbraco site at local address like https://192.168.100.30:44309 or https://127.0.0.1:44309 and I click on continue to confirmation page after payment (invoing or paypal or stripe), i am redirected to an incorrect url like this https://192.168.100.30/umbraco/vendr/payment/continue/invoicing/e963882b-369a-47d2-a618-9c4daf2ff100/ORDER-0589-0513-MKZ8/7db53b3770723d7aa30c3c10d7926f36dfbe2788649f027d7
I noticed that if I deploy to an address like https://127.0.0.1:44309 (or https.//192.168.1.31:44309), then the port is missing in the redirect url. I think that it may be a bug: Vendr fails to create redirect url in case it contains both numbers and port. Any help is appreciated
What version of Vendr are you using?
1.8.4
Ok, I've just looked into this and yea, it does appear that we have some code that says if it's on https and you aren't on localhost it's just always setting the port to 443.
Unfortunately there isn't a code comment as to why we did that so I'm not sure why we needed that. I'll create a bug report for this and get it updated in the next release, but until then you might try using something like nip.io or ngrok to give you a temporary URL to view the site on.
Matt
Ok, i can also solve the problem deploying the website on port 443 (the standard port of https). Is it right?
Yup, that's right 👍
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.