v20 cannot send emails after upgrade from v18 = 5.7.0 Denied

BthPOA

Premier Customer
Joined
Feb 19, 2024
Messages
7
Reaction score
0
Hi,

I realize, looking at https://portal.3cx.com/ that our licence after upgrade from 18 to 20, lost the FQDN and maybe it's the main reason to not be able to send emails.

How can we contact 3CX team in order to fix it?
 
Hi, yes, you need to reinstall the system and set a new fqdn, without that you can't use external services such as the 3cx smtp.
 
Hi,

server reinstalled and I used the option to 'restore' form a backup, but shows this message: FQDN already in use. Please choose another one.

Since I´m login to my account at 'https://portal.3cx.com/customer/systems', there is no FQDN in use for the subcription. Why this message appears??


1751730680840.png
 
Last edited:
I found an old thread about 'FQDN release' but right now in the portal, there is no option for that on menu.

 
I don't know if that issue is related with old subscription (2024 ~ 2025) which is still listed on the portal but there is no option to 'release FQDN'

1751738365915.png
 
The current subscription: the same issue with no option to release the FDQN

1751738558772.png
 
Hi 3Cx team,

as a customer, I would like to suggest to create a new collumn to display the FQDN directly without need click on the system to obtain that information.;)

1751740740444.png
 
Hello,

As I see you are using a custom FQDN? Could you please try to setup as new with your FQDN, not restore from backup in the portal, and then after it is setup do a restore.

The backup you are restoring from is V20, yes?
 
Hi 3Cx team,

as a customer, I would like to suggest to create a new collumn to display the FQDN directly without need click on the system to obtain that information.;)
Hi,

For this specifically, if the FQDN is setup it does show :)
1751865667299.png
 
  • Like
Reactions: Evolute IT
Hi @KyriacosS_3CX,

that is the problem, our custom FQDN are not shown in the portal ('my system') but when we try to restore shows a msg related with 'FQDN is already in use'.

Answering your question, 'yes' the environment is v20 with a custom FQDN.

Questions
#########
1) Can you (or 3CX team) do a internal research and release the FQDN at your side since we cannot do via portal (my system)?
2) Could we remove the old version (expired one) listed in the portal?? I think that it is the main issue.
 

Latest Posts

Forum statistics

Threads
111,962
Messages
589,971
Members
164,864
Latest member
SCarpenter@fifthavenue-la