[SOLVED] EVE-Pro 6.2.0-6 cannot edit "configured objects"

Before posting something, READ the changelog, WATCH the videos, howto and provide following:
Your install is: Bare metal, ESXi, what CPU model, RAM, HD, what EVE version you have, output of the uname -a and any other info that might help us faster.

Moderator: mike

Post Reply
mamakos
Posts: 57
Joined: Thu Dec 19, 2019 4:49 pm

[SOLVED] EVE-Pro 6.2.0-6 cannot edit "configured objects"

Post by mamakos » Tue Aug 20, 2024 1:39 pm

Hello,

Since we upgraded from EVE-NG Pro 5.x to 6.2.0 I cannot edit the shapes anymore.
I can add objects (text, custom shapes, etc.) but :
  • Text does not have any Rich HTML Office Option
  • Once they are added I cannot modify the color/parameters anymore
When I close the lab and reopen it, I can access the right-click drop-down menu but only once for the first object. But still the "edit" option only displays the "position" parameters (never the shapes, color, font, etc.)
Screen Shot 08-20-24 at 03.19 PM.PNG

Then when I right-click a text/shape object I do not have the drop down menu anymore until I close/reopen the lab.
Screen Shot 08-20-24 at 03.18 PM.PNG


I have the same behaviour with Firefox and Edge
I have the same behaviour with a brand new lab or a former lab (created in the 5.x release)
I have the same behaviour with a "native console" or an "HTML5 console" login manner
Other administrators have the same issue

For routers the right-click drop down menu works fine.

The only way to remove a configured object is this way
Screen Shot 08-20-24 at 03.22 PM.PNG
Is this a regression or is there anything that I am missing ?
You do not have the required permissions to view the files attached to this post.
Last edited by mamakos on Wed Sep 11, 2024 8:36 pm, edited 1 time in total.

Uldis (UD)
Posts: 5177
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:

Re: EVE-Pro 6.2.0-6 cannot edit "configured objects"

Post by Uldis (UD) » Tue Aug 20, 2024 5:48 pm

It is text object and you CAN edit it,
Or this lab is imported from EVE Community where such object is not editable

And serious advice, CLEAN your browser cache and cookies !!!!
You do not have the required permissions to view the files attached to this post.

mamakos
Posts: 57
Joined: Thu Dec 19, 2019 4:49 pm

Re: EVE-Pro 6.2.0-6 cannot edit "configured objects"

Post by mamakos » Wed Aug 21, 2024 2:35 pm

Hello Uldis,

1) The lab is NOT imported from an EVE-Community release. It was created in a past EVE-PRO 5.x release. I upgraded the cluster to 6.2.0 last week. As I also stated, the issue is also present with a FRESH lab created directly from EVE-PRO 6.2.0-6. We have an "admin" role so we should not be blocked by any restriction as far as I understand. the lab are mine (not shared).
2) I did clear cookies/cache from Firefox (115.14.0esr (64 bits)). Same result.
3) I did clear cookies/cache in Edge (Version 126.0.2592.113 (64 bits)) without any more success.
4) I also tried with a private tab from Firefox. same issue.

So we can modify the text but not its font/size/color/etc. Same with the other objects once they are created.

View with Firefox :
Screen Shot 08-21-24 at 04.17 PM.PNG
View with Edge :
Screen Shot 08-21-24 at 04.22 PM.PNG
Proof of release :
Screen Shot 08-21-24 at 04.27 PM.PNG
You do not have the required permissions to view the files attached to this post.

Uldis (UD)
Posts: 5177
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:

Re: EVE-Pro 6.2.0-6 cannot edit "configured objects"

Post by Uldis (UD) » Wed Aug 21, 2024 4:34 pm

try double click on that text obgect, it must pop up the html word editor tool.
right click and edit, will do exactly what you showing in your screens.

anyway if still problems join:

For the best and fastest support or any other questions please join in the EVE-NG live support:
https://webchat.eve-ng.net/login/
Use your Gmail account to login, or create new chat account with own email.

mamakos
Posts: 57
Joined: Thu Dec 19, 2019 4:49 pm

Re: EVE-Pro 6.2.0-6 cannot edit "configured objects"

Post by mamakos » Fri Aug 30, 2024 10:38 am

I may have a clue. When I activate the debug mode on Firefox I have a fobidden access to janus/janus.js file. It seems to be the file called when we try to edit an object (text/square/etc.)
When I search for this file in the directories there is a logical-link to a non existent location (/opt/janus/share/janus/demos/). There is no subdirectory "janus" under /opt

Could this be the reason of this failure ? Can we simply copy the files ?

Code: Select all

root@muztc628:/opt/unetlab/html# ls -al
total 584
drwxr-xr-x 12 root root   4096 Aug 16 08:47 .
drwxr-xr-x 17 root root   4096 Aug 16 08:47 ..
-rw-r--r--  1 root root 514542 May 19 15:19 api.php
-rw-r--r--  1 root root    128 Aug 30 11:21 blob
drwxr-xr-x  2 root root   4096 Aug 16 08:47 configs
drwxr-xr-x  3 root root   4096 Aug 16 08:47 doc
-rwxr-xr-x  1 root root   1034 Aug 16 08:55 eve-ng.lic
-rw-r--r--  1 root root   1034 Sep 29  2022 eve-ng.lic.bkp
-rw-r--r--  1 root root    688 Oct 11  2023 eve-ng.lic.legacy
-rw-r--r--  1 root root    578 Feb 22  2024 eve-ng.nolic
drwxr-xr-x  2 root root   4096 Aug 16 08:47 favicon
-rw-r--r--  1 root root   1150 Feb 22  2024 favicon.ico
drwxr-xr-x  2 root root   4096 Aug 16 08:47 files
-rw-r--r--  1 root root   1582 Feb 22  2024 .htaccess
drwxr-xr-x  4 root root   4096 Aug 16 08:47 images
drwxr-xr-x  4 root root   4096 Aug 16 08:47 includes
lrwxrwxrwx  1 root root     29 Feb 22  2024 janus -> /opt/janus/share/janus/demos/
-rw-r--r--  1 root root     72 Jul 24 18:39 pattern
drwxr-xr-x  2 root root   4096 Aug 16 08:47 rdp
lrwxrwxrwx  1 root root     15 Dec 17  2021 sat -> /etc/eve-agent/
drwxr-xr-x  5 root root   4096 Aug 16 08:53 templates
drwxr-xr-x  2 root root   4096 Aug 16 08:47 templates_legacy
drwxr-xr-x  5 root root   4096 Aug 16 08:47 themes

root@muztc628:/opt/unetlab/html# ls -al /opt/
total 80
drwxr-xr-x 20 root root 4096 Aug 16 08:54 .
drwxr-xr-x 21 root root 4096 Aug 16 08:43 ..
drwx--x--x  4 root root 4096 Dec 17  2021 containerd
drwxr-xr-x  2 root root 4096 Aug 16 08:54 dockers-src
drwxr-xr-x  2 root root 4096 Aug 16 08:47 ovf
lrwxrwxrwx  1 root root   10 Feb 27  2024 qemu -> qemu-2.4.0
drwxr-xr-x  6 root root 4096 Aug 16 08:45 qemu-1.3.1
drwxr-xr-x  9 root root 4096 Aug 16 08:46 qemu-2.0.2
drwxr-xr-x  6 root root 4096 Aug 16 08:46 qemu-2.12.0
drwxr-xr-x  9 root root 4096 Aug 16 08:45 qemu-2.2.0
drwxr-xr-x  8 root root 4096 Aug 16 08:45 qemu-2.4.0
drwxr-xr-x  6 root root 4096 Aug 16 08:46 qemu-2.5.0
drwxr-xr-x  6 root root 4096 Aug 16 08:45 qemu-2.6.2
drwxr-xr-x  6 root root 4096 Aug 16 08:45 qemu-3.1.0
drwxr-xr-x  6 root root 4096 Aug 16 08:46 qemu-4.1.0
drwxr-xr-x  6 root root 4096 Aug 16 08:46 qemu-5.2.0
drwxr-xr-x  7 root root 4096 Aug 16 08:45 qemu-6.0.0
drwxr-xr-x  7 root root 4096 Aug 16 08:45 qemu-7.2.9
drwxr-xr-x  7 root root 4096 Aug 16 08:46 qemu-8.2.1
drwxr-xr-x 17 root root 4096 Aug 16 08:47 unetlab
drwxr-xr-x  3 root root 4096 Aug 16 08:46 vpcsu

mamakos
Posts: 57
Joined: Thu Dec 19, 2019 4:49 pm

Re: EVE-Pro 6.2.0-6 cannot edit "configured objects"

Post by mamakos » Tue Sep 03, 2024 9:26 am

OKAY, we found out what was the issue.
The problem is that the API used to generate the rich formating text pop-up uses now the physical IP address of the master instead of the FQDN like it did in release EVE-Pro 5.x
Since we are using an NGINX reverse proxy between us and the server we had to modify its configuration by adding a sub_filter rewrite rule.
We already had to tweak it for guacamole.

Is there a configuration file to get EVE-NG use the FQDN instead of the IP address? (like it did in 5.x)

Code: Select all

                ########################
                ## Location Guacamole ##
                ########################
                location /html5/ {
 
                        set $app_auth ga-eveng-pro;
                        auth_request /authapp;
                        error_page 401 = /ErrorPage;
 
                        proxy_http_version 1.1;
                        proxy_set_header Upgrade $http_upgrade;
                        proxy_set_header Connection "upgrade";
                        proxy_set_header X-Forwarded-Host $host:$server_port;
                        proxy_set_header X-Forwarded-Server $host;
                        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                        proxy_pass http://<physical_IP_address>:8080/guacamole/;
               }
 
                location /html5/websocket-tunnel {
 
                        set $app_auth ga-eveng-pro;
                        auth_request /authapp;
                        error_page 401 = /ErrorPage;
 
                        proxy_http_version 1.1;
                        proxy_set_header Upgrade $http_upgrade;
                        proxy_set_header Connection "upgrade";
                        proxy_set_header X-Forwarded-Host $host:$server_port;
                        proxy_set_header X-Forwarded-Server $host;
                        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                        proxy_pass http://<physical_IP_address>:8080/guacamole/websocket-tunnel;
                }
 
                ###########################
                ## Location Catch all             ##
                ###########################
                location / {
 
                        set $app_auth ga-eveng-pro;
                        auth_request /authapp;
                        error_page 401 = /ErrorPage;
 
                        proxy_set_header X-Forwarded-Host $host;
                        proxy_set_header X-Forwarded-Server $host;
                        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                        proxy_set_header X-Forwarded-Proto $scheme;
                        proxy_set_header X-Real-IP $remote_addr;
                        proxy_set_header Host $host;
                       
                        # Adding this for rich text format pop-up API (and custom shapes)
                        sub_filter 'https://<physical_IP_address>' 'https://eve-ng-pro.my.fqdn.com';  <<<<<<<<<<<<< THE NEW LINE
 
                        proxy_pass https://<physical_IP_address>;
                }
        }

Post Reply