eab

@Marcos by now I think it should be obvious that there is a problem specifically with the Linux version of WAP and not the Windows version.
Like I already said - disabling WAP entirely is the only way (other than stopping the eea service entirely) to load the website (in Chrome and/or FF).

Look like here at my company, we are affected by the same exact behavior @eab described in this thread...
Like @eab, as an enterprise customer, I am very surprised that problem stay in « backlog », since to be able to use services listening on « localhost » for all of our developer's, it imply to disable completely the WAP security on all of our Linux clients running the product...
 
I am now following this topic, thanks to @eab for the detailed behavior described here...

Yes, that's the last reply I received from Mr. Schwalb on the 13.12.23. It doesn't say anything other than "we have reproduced the issue and will fix it at some point in time".
As a business using ESET for PC security, I expect a bit more in the way of a timeline of this problem being fixed - a problem which is so severe it makes WAP harmful to productivity (for Linux users), where it really should not. And for that kind of problem I expect something a lot more concrete from the developer of the software.

I've reached out to the product manager with a reference to this topic and asked to look into it with higher priority, if possible.

Yes, that's the last reply I received from Mr. Schwalb on the 13.12.23. It doesn't say anything other than "we have reproduced the issue and will fix it at some point in time".
As a business using ESET for PC security, I expect a bit more in the way of a timeline of this problem being fixed - a problem which is so severe it makes WAP harmful to productivity (for Linux users), where it really should not. And for that kind of problem I expect something a lot more concrete from the developer of the software.

Hey, thanks so much! I was wondering if that wasn't the solution. 💫

Hi eab,
Endpoint service fails to start, because of error in module compilation. This is caused by missing 'gcc-12', installation of this package should resolve this issue. Please try to install gcc-12 and start eea service again. 
"Compilers differs warning" tries to tell you, that there are differences in version of compiler used to build kernel and currently found compiler. There should be no impact on Endpoint functionalities if module compilation is successful. 
Regards,
Kurco

@kurco we already have a ticket open with our local ESET supplier. We are preparing the necessary logs they requested. Will keep you posted ... 

Could you please elaborate more? I see v9.1.4.0 in your screenshot.

Thanks for sharing Marcos. 
Even if there are delays, I, myself, and I'm sure many others would appreciate the fact that this information is shared with them to be aware fo roadmap changes and estimates (emphasis on estimate, I am aware first hand how sometimes bugs can be found and time table can be pushed back to fix the product before actual release.)
 

Ubuntu 22.04 LTS will be supported as of the managing agent v10. ESET PROTECT v10 is going to be released tomorrow.
Also we're going to discuss ways how to better proactively inform you about planned support of new operating system as we understand it is important to have this information especially in business environment.

It's as if you didn't actually read what I wrote (and what you quoted). 🙄
Nothing in your post deals with the issues I raise.
You show a screenshot and a source link - however, your link goes to the following page/information (No 'Ubuntu 22.04' there):

But even if the information was updated on that page, how does this deal with the point of 'pro-active, timely, and professional communication'?
Furthermore, as of right now there is still no information on https://support-feed.eset.com/news/ or on https://support-feed.eset.com/advisories/ about the latest release of ESET Endpoint for Ubuntu 22.04, so why are you promoting these sources as a solution to the problem of lacking 'pro-active, timely, and professional communication'!? 🤔

You're giving another good example of a site that needs to be searched on a timely basis in order to find any updates (which means we, the customers, need to keep track of version changes to find out what's the latest&greatest, and guess when it was released (doesn't say on that page anywhere, so I need to go to another location to find when it was released) 

Bottom line, your help here, is great if I want to be the proactive one for ESET. 
Which I don't, I'm a business customer, not an employee, or retailer.  

With all due respect, while this forum may not take the place of 'creating a support ticket', it is generally understood that the official forum board of a company is there to provide official feedback to customers for things which do not require individual support tickets to be created - for example when it's obvious that the issue is not due to a specific case, but is something which multiple customers are dealing with - such was the case with this particular issue.
As for the official announcements feed which you linked to (https://support-feed.eset.com/news/) - it has been noted previously that there has been zero pro-active communication through any means or method which has informed the business customers about anything whatsoever related to Ubuntu 22.04 + ESET Endpoint.
In fact, as I am writing this I find that the last post on that support feed pertaining to ESET Endpoint for Linux seems to have been on May 2nd 2019. 👀  Additionally, there seems to have still been no post regarding the release of Endpoint for Ubuntu 22.04 - same for the information displayed in my ESET PROTECT web console dashboard. 👀👀
So, again, there is in fact a real problem here with a lack of pro-active, timely, and professional communication, and this should be taken seriously instead of ignored or excused away. Take it or leave it. Up to you.

Thanks for explaining Marcos on why my post was removed. 
I understand your relation to capital letters and exclamation marks,. 
Please understand that most of those mentions were not directed personally to you, but to the procedure ESET descides to present itself in this forum.  - which as you might understand can be frustrating to receive as a customer. (an advanced user of ESET is still a customer)

I would only be brief to say, some of these capitalized words and exclamation points were directed to you, even though they were a little out of line  (My apologies for that.) 
Your behaviour in this thread as an official employee of ESET and someone who holds the responsibility of an Administrator and staff of this forum. was disrespectful, filled with excuses, and completely not what I would expect from customer service (especially when I come from this line of work.
Own to your responsibility please. If you decided to answer my question 6 days ago, and I made a follow up requesting your help with dropping a message in the thread (because you can't follow the entire section for version release notes) 
Either tell me you are not doing that, or you are. sorry to say mate, but if you are responding to me, you should give the decensy to respect a customer and a user in this community and reply that you will, or not. 
and if you don't reply, I take it as a confirmation. 
 
one last thing, what's this note above my post? a punishment? I don't recall seeing it before.

Mate, what do you mean 'already'? I informed the users in this thread 20 minutes before you made your announcement thread. 
I agree 100% with @avielc in that business customers should not be expected to have to go out of their way to be informed of software release updates etc ... Our Email address is already registered with ESET, so please use it for something other than telling us when our license renewals are due. 😜

Mate, what do you mean 'already'? I informed the users in this thread 20 minutes before you made your announcement thread. 
I agree 100% with @avielc in that business customers should not be expected to have to go out of their way to be informed of software release updates etc ... Our Email address is already registered with ESET, so please use it for something other than telling us when our license renewals are due. 😜

Had I not been following this topic then I would not have been aware of this upgrade.
Eset should be pushing out this upgrade information to business customers. Customers using this product will have registered and as part of the registration process, a customer provides an e-mail address.
Other software companies advise registered users that an upgrade is available.

@Marcos @TomasP @JamesR @Peter Randziak
So, should I say, here is an example where we asked for an update and didn't get it? 
Do we really have to find out by ourselves it is out? (Seen it half an hour ago on the Console by accidentally checking it) 
This is really REALLY bad reputation for ESET. Is there anyone we can escalate this to? 
 
Also, @eab - I suggest doing small batch tests first, I get skeptical with every new version lately.

By the way everyone ... it's been released!!
https://www.eset.com/int/business/download/endpoint-antivirus-linux/

😂😂 Do you work for ESET? LOL!

I agree with avielc and eab's well presented rational comments.
Eset has no idea how businesses function and they fail to comprehend our needs.
 

I think you are missing the point here mate. 
No one from ESET made any attempt to mention any release of a new version or that there has been any changes that might affect the current version. 
Instead all of us here, had to dig through the net to try and debug the ESET R&D Team error messages and figure out what's wrong with installations on 22.04. 
This is a really bad (not the worst, unfortunately I've seen worse) customer service of how to share information and help your customers prepare ahead of time. 

On that note, the error messages can be so unclear and the lack of information on errors that could occur to anyone on the range of ESET business products. really must have me, a client have to dig through a forum where the answers are given on separate threads that would require extensive digging and waste of time on my end. 
Not to mention some errors are just generic errors I actually find answer to on the web instead of ESET. 
Only shows how the support segment of ESET is disorganized, and is left for the community to help one another.  
I will add the staff can be helpful sometimes. However, I expect some better ways to make the common errors or at the very least, a list of these error codes to be published somewhere. 
After all these were made by R&D for them to make it clear to understand what the error is, so make a list of what it means and attach it to some ESET KB. <- you can have this idea for free, this time.

Thanks. Better late than never I suppose. 😒
Both of you have completely missed the point. 🤦‍♂️
Let me try to explain this to you once more as clearly as I possibly can.
Businesses are looking for products and services, which are as reliable as possible, to use in their business environment.
Being reliable not only means, in the case of software, that it runs stably and functions correctly, and that it is well documented, but also that the company developing the software is proactive with informing the customers about such things as critical updates and bug-fixes, as well as when to expect the next releases (release schedule) - especially when concerning major releases. Why is this latter information important?
Because businesses with 100s or 1000s of licences will need to plan ahead for roll-outs, and when Apple, Microsoft, Canonical, etc ... announce months in advance that they have a new OS being released, a businesses IT team will begin to discuss the strategy for migrating to the new OS, and then the question will immediately arise "What is our Endpoint provider doing about the new OS?". 
In the case of ESET and Ubuntu 22.04 the proactive communication to your business customers was, as far as I know, totally non-existent. In plain words, you guys are just sitting on your proverbial communicative hands with the attitude of "Well, if any of our customers are interested enough, they can spend their time searching online until they either eventually stumble across a forum thread that deals with this matter or have to create a new forum thread themselves. We just cannot be bothered to spend a mere 5 minutes of our time writing an official communication regarding the matter." It comes across as incredibly unprofessional.

Thanks. Better late than never I suppose. 😒
Both of you have completely missed the point. 🤦‍♂️
Let me try to explain this to you once more as clearly as I possibly can.
Businesses are looking for products and services, which are as reliable as possible, to use in their business environment.
Being reliable not only means, in the case of software, that it runs stably and functions correctly, and that it is well documented, but also that the company developing the software is proactive with informing the customers about such things as critical updates and bug-fixes, as well as when to expect the next releases (release schedule) - especially when concerning major releases. Why is this latter information important?
Because businesses with 100s or 1000s of licences will need to plan ahead for roll-outs, and when Apple, Microsoft, Canonical, etc ... announce months in advance that they have a new OS being released, a businesses IT team will begin to discuss the strategy for migrating to the new OS, and then the question will immediately arise "What is our Endpoint provider doing about the new OS?". 
In the case of ESET and Ubuntu 22.04 the proactive communication to your business customers was, as far as I know, totally non-existent. In plain words, you guys are just sitting on your proverbial communicative hands with the attitude of "Well, if any of our customers are interested enough, they can spend their time searching online until they either eventually stumble across a forum thread that deals with this matter or have to create a new forum thread themselves. We just cannot be bothered to spend a mere 5 minutes of our time writing an official communication regarding the matter." It comes across as incredibly unprofessional.