[jlaunch] Joomla.com Update mails contain confusing url

[coolcat-creations]

See screenshot:

[HLeithner]

@dmitriy-cloudaccess we have some issues reported for joomla.com in this repo, are you the right person which can help on this topics? https://github.com/joomla/joomla-websites/issues?q=is%3Aissue+is%3Aopen+joomla.com

[Pawel-Panek]

Please tag @Pawel-Panek or @dereksca for launch.joomla.org provisioning issues.

@coolcat-creations can you edit the tile to have [jlaunch] in front?

The problem with this notification has been discussed widely here: https://github.com/joomla/joomla-cms/issues/35600 .

[Pawel-Panek]

@coolcat-creations I mean for all those issues related to LJO posted recently by you. The title should start with [jlaunch] so we can easily filter them. Thank you.

[HLeithner]

@Pawel-Panek thanks for the info, I added jlaunch to all of the issue I could found and tagged you in an old one. If you or a colleague thinks a issue can be closed please tag me or @pe7er

[brianteeman]

This ip6 issue has been ongoing for several years

[Pawel-Panek]

That's not related to the IPv6 access. The thread regarding this notification has been started in here: https://github.com/joomla/joomla-cms/issues/35600

@coolcat-creations I think this one can be closed as the issue is about Joomla CMS and not the launch site.

[HLeithner]

I reopened the relevant PR at the cms https://github.com/joomla/joomla-cms/issues/35600 and close this one, thanks @Pawel-Panek

[HLeithner]

for the meantime @Pawel-Panek could you maybe add the live_site parameter, would this work for you?

[brianteeman]

commenting here as I am unable to comment on the other issue.

this is a server configuration issue and not a joomla issue

[HLeithner]

more or less true, but we have the same problem in joomla 4 with cli scripts and as mentioned could be fixed by setting live_site parameter

[brianteeman]

could be fixed by setting live_site parameter

should be fixed by the borken host

[HLeithner]

that's the reason why I ask pawel if they can fix it.

[brianteeman]

if they can't then its just another reason not to use them and to find a better provider

[brianteeman]

@Pawel-Panek Why is this only an issue for cloudaccess and not for any other host?

[HLeithner]

It's an issue for any other host, that allows to access the website by IP and has nothing explicit to do with cloudaccess it self only with the configuration.

If you open https://[2607:1b00:93b2:e42c::2e88]/ you will see the website. Since I don't have IPv6 on this connection I can't check.

I'm not sure if you can use an arbitrary domain, can you confirm that this not possible? if it's possible you have a bigger problem.

[brianteeman]

It's an issue for any other host, that allows to access the website by IP and has nothing explicit to do with cloudaccess it self only with the configuration.

Exactly - its a server configuration issue that no other host is configuring their server as.

If you open https://[2607:1b00:93b2:e42c::2e88]/ you will see the website. Since I don't have IPv6 on this connection I can't check.

I am in a hotel right now so dont have ipv6 here either. But it really doesnt matter which protocol is being used. The server should only be responding to the name not the ip address

if it's possible you have a bigger problem.

Starting with the fact that you can not get an ssl certificate for an ip address

[HLeithner]

Starting with the fact that you can not get an ssl certificate for an ip address

fact? sorry that's wrong it's possible to get a ssl certificate for an IP

[brianteeman]

fact was used as an expression (ot)

only from limited providers and only by the person that owns the ip address