Problems with accessing team server for 5.8.1

0
When using 5.8.1 version of the modeler, my project seems to be unable to get updates from the team server when I am using a proxy server. With version 5.4.1 I didn't have such problem. Is this a known issue?
asked
3 answers
0

Can you share more details about this?

  • What exact error messages do you get?
  • Since when do you see these problems?
  • Does the modeler version actually matter? Is using 5.4.1 succesful, while using 5.8.1 fails, when you're using exactly the same proxy settings? Or do both fail? You say "I didn't have", can you try starting a 5.4.1 project again to reproduce the issue?
answered
0

Hi Hans,

I actually realized that my problem holds for all versions of the modeler, when trying to connect via proxy server.

In details: when trying to open a project in the modeler "from the team server", I get a pop-up screen with just an "x" red button (like error, but with no text). I can only click "ok". Steps I follow to reproduce it (with any version of the modeler): a) Create a new project at the team server b) Open modeler (any version) and open project "from the team server" c) Initially, I get the "x" error screen described above d) When I click "ok", my "open" screen says that I don't have the project on disk yet and I have to chose the folder where it will be located (logical, as it's the first time I try to open it) e) When I chose folder and click ok, nothing happens. When trying to repeat the process after that, same things happen.

Also, when opening existing apps, I am not able to commit/update changes from the team server. Is this expected when connecting via proxy server? (I tried ports 8080, 8081, 8082 for the proxy configuration, I got the same issues). How can I still use team server when connecting via proxy?

answered
0

Ok, I suggest opening a support ticket for this. There may be incompatibilities with the combination of your proxy server software and the way Mendix provides online services.

All connections to Mendix use https. Do you know if your proxy server allows the usage of https (I hope so..) and if it's allowing traffic to go through unmodified? If the proxy wants to look inside traffic, is has effectively to do a Man in the middle attack on your connection, presenting an invalid SSL certificate. Might that be the problem? The modeler not trusting the connection? Even if that works, the proxy might be over-paranoid, blocking requests other than GET and POST?

There are a lot of possibilities for things to go wrong when using proxy servers...

Hans

answered