Salut Franck,

Tu veux parler de la nouvelle version Preview en cours 2021.4.1 ? Si oui tu n'est pas dans la bonne partie du forum. Je peux changer l'emplacement de ta demande si tu me confirmes bien la chose... ...

Si cela concerne la 2021.3.5 on reste sur cette page "Question"...

J'espère que tout baigne pour toi depuis tout ce temps.

@Suivre,

J.P.

Hey,

Salut JiPé, non je parle de la version officielle en "production" 2021.3.5 (qui est bien une version non aboutie d'ailleurs) puisque des bugs relevés ici depuis plus de 3 ans y figurent toujours ;-)

Je vois que tu es toujours fidèle au poste !

Bonne journée

Franck

Hello Franck

I am afraid that the situation is still the same as back them. After analyzing the situation, we've concluded that the Virtual Machine wasn't configured correctly to allow the software to work as expected.

Since no progress was done on the matter since then, I'll report the answer given at the time again here for reference:

Unfortunately, it looks like nothing can be done software-side to make this different. The VM must own an IP that is accessible from outside, which would not be right even if it had the same IP as the host machine.

It definitely required further study in the VM settings in order to allow the VM to obtain an IP which is reachable from outside its environment. Unfortunately we cannot grant the support on this matter, so I'm afraid you will need to dig deeper into this matter specifically on the VM settings.

Please feel free to get back to me if I could provide any further clarification to you.

Thank you for your understanding

Stefano

GOOGLE TRANSLATE ---

Bonjour Franck

Je crains que la situation ne soit toujours la même qu'à leur retour. Après avoir analysé la situation, nous avons conclu que la machine virtuelle n'était pas configurée correctement pour permettre au logiciel de fonctionner comme prévu.

Puisqu'aucun progrès n'a été fait sur la question depuis lors, je vais rapporter la réponse donnée à l'époque à nouveau ici pour référence:
Malheureusement, il semble que rien ne puisse être fait côté logiciel pour rendre cela différent. La VM doit posséder une IP accessible de l'extérieur, ce qui ne serait pas correct même si elle avait la même IP que la machine hôte.

Cela nécessitait certainement une étude plus approfondie des paramètres de la VM afin de permettre à la VM d'obtenir une IP accessible depuis l'extérieur de son environnement. Malheureusement, nous ne pouvons pas accorder l'assistance à ce sujet, je crains donc que vous deviez approfondir cette question en particulier sur les paramètres de la machine virtuelle.

N'hésitez pas à revenir vers moi si je peux vous apporter d'autres éclaircissements.

Merci pour votre compréhension

Stefano

Hello Stefano,

Not agree, but really NOT.

Look at a network adpators list here on ONE PC... Configured with many other solutions.

Do you think it is our role to check with each solution on how to configure the IP, because your software cannot get the good one.

It's WSX5 which needs to catch the good IP. Other solutions are working fine without WSX5. So it is YOUR ROLE to find a way to get the good IP.

I am definetively not agree with you... and like this BUG because it is a BUG is not often discussed, no fix has been done since 3 yrs  !!!!

Does it acceptable when we paid update protection. Your role is to fix any issue and not to say: 

I'm afraid you will need to dig deeper into this matter specifically on the VM settings.

Your answer is not acceptable... 

So hope to see any enhancement about this one.

Enjoy!
Axel

Hello Stefano, Hello Axel,

Agree, but very agree with Axel.

I don't think you understand the problem.

It has nothing to do with the setting of the IP that can be reached from outside!

We are talking about local ip.

I had given three years ago a way to follow with the c++ function (with which wx5 is developed) GetAdaptersInfo!

If this is beyond you... let us choose to manually set the ip of the ad hoc network card in the software.

Franck

Hello everyone

I might have explained myself the wrong way but I would like to point out exactly why this issue specifically is most definitely an issue with the current Virtual Machine and not with Virtual Machines in general.

The fact that I can safely state that WebSite X5 can work correctly on VMs is that we already have different customers doing this.

This means that the software can in fact, safely run on those. If in your case specifically, this doesn't seem to be working right, it must be related to the VM configuration taken under consideration, or it simply wouldn't work for anyone

The official support cannot provide assistance for this, since this extends over what can be considered an issue of the software specifically and needs to be addressed with the VMs assistance specifically

Thank you

Stefano

I think you don't understand our request

The exact bug is :

Mobile preview does not work if you have virtualization software installed on the machine (lan card confusion)

The bug is NOT :

Mobile preview does not work on a virtual machine

and wx5 don't run on a virtual machine but on a computer with a virtualisation software installed !

cqfd

Hello Franck

I thank you for your clarification

Unfortunately, the translation must have must things unclear and I would definitely like to ask you for more information about this.

Do you say that as soon as I install software such as Virtualbox on my machine if I try to run the QR preview on the software in the real machine, it won't work? With certainty?

If you uninstall Virtualbox just temporarily and try again, it starts working immediately?

Please keep me posted here

Thank you

Stefano

Hello Stefano,

I am very happy that 3 years after the first report of this bug, you have understood the problem, despite the clearest explanations of Axel and myself.

I confirm that the installation of a virtualization software (which will create virtual network interfaces) such as virtualbox, vmware, etc, will create the problem. Simply uninstalling these will remove the virtual network interfaces and thus the wx5 qrcode will work.

I had given you a hint with the GetAdaptersInfo in 2018 and in this post to be able to "filter" the network interfaces on the workstation... It remains for the devs to do their job since 3 years ;-) And if it's too much to ask, have at least one parameter to enter to do the configuration manually, i.e. tell wx5 the ip address of the correct interface to generate the good QRcode.

Thanks

Franck

Hello Franck

Right now, I've performed a few tests with this while having a Virtual Machine install and running on the device and I'm able to use the QR code correctly anyway.

Of course, this does not exclude that the issue can pop up in specific conditions. I've notified the developers of this to investigate the matter further

Should there be news on this, I will keep you posted here

Thank you

Stefano

Hello Stefano

Happy to know that !

But for me on 2 computers with virtualbox and vmware I have the problem and it seem Axel too.

I look forward to hearing from the support

Regards

Franck

Hello Franck

I've verified the issue with the developers and the fact that this can work or not is basically very random. It entirely depends on the order with Windows lists the network adapters and without the possibility of understand which one is the real one automatically

That being said, since by design we want to avoid having the user choose the correct one, you can navigate to:

C:\Users\your username\AppData\Local\Incomedia\WebSite X5 - Your Version

and open the Config.xml file. You can insert the correct IP here and it will be used by the preview instead

Please proceed like this and let me know if it works like this

Thank you

Stefano

Hey Stefano,

Generally the network card which should be the good one would be this one which has an IP gateway and IP DNS.

Others NIC's are generally just with one IP and nothing more.

Look at my picture previously.

So it could be a good way to detect the good NIC... (the PC could be installed with 2 or 3 NIC's with different gateways / DNS.. it is true, but no common !!!! maybe on servers into a Data Center, but not really at home or office on laptop or desktop PC)

So in this case Dev team could be change something to accurate NIC detection.

Enjoy!
Axel

Re,

Oui en modifiant le config.xml : ça fonctionne !

La solution d'Axel est une solution... ou tout simplement éliminer les noms d'adaptateurs qui contiennent le nom du logiciel installé. Personnellement pour moi, j'ai les 2 noms vmware et virtualbox dans le nom des adaptateurs.

++

Franck