Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

zammad on CentOS7 - after update zammad no working again! #1269

Closed
ruebenmaster opened this issue Jul 18, 2017 · 43 comments
Closed

zammad on CentOS7 - after update zammad no working again! #1269

ruebenmaster opened this issue Jul 18, 2017 · 43 comments
Assignees

Comments

@ruebenmaster
Copy link

Hallo people,
today i made an update because of security. I used a virtual machine on vmware 6. Linux distribution is CentOS7. ( yum update )
now it is the third time, zammad doesn't start after update to 1.6.1. the nginx don't show it anymore...
zammad.zip

The installed version is: 1.6.1-1500274100.a9a76ef.centos7
The installation was done exactly the howto on zammad.org. (where 1.5.0 is titeld as the newest version)
CentOS version: Linux version 3.10.0-514.26.2.el7.x86_64 (builder@kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Tue Jul 4 15:04:05 UTC 2017

in attachment the production logfile... Now i try it on opensuse 42.2. if it fail too, zammad is dead for production use...

greetings
Stephan

@thorsteneckel
Copy link
Contributor

Hi Stephan,

looks to me like something went wrong while performing the database migrations. Might be a duplicate of #1261.

Could you please run zammad run rake db:migrate on your affected CentOS7 VM and post the output here.

Thanks!

@thorsteneckel thorsteneckel marked this as a duplicate of #1261 Jul 18, 2017
@ruebenmaster
Copy link
Author

Hallo Thorsten,
here the list:

[root@zammad ~]# zammad run rake db:migrate
== 20170525000001 ReplyToSenderFeature: migrating =============================
== 20170525000001 ReplyToSenderFeature: migrated (0.0774s) ====================

== 20170525000002 FixedTwitterTicketArticlePreferences: migrating =============
== 20170525000002 FixedTwitterTicketArticlePreferences: migrated (0.0226s) ====

== 20170529000002 SettingDeliveryPermanentFailed: migrating ===================
== 20170529000002 SettingDeliveryPermanentFailed: migrated (0.0260s) ==========

== 20170529132120 LdapMultiGroupMapping: migrating ============================
== 20170529132120 LdapMultiGroupMapping: migrated (0.0023s) ===================

== 20170531144425 ForeignKeys: migrating ======================================
-- rename_column(:ticket_flags, :tickets_id, :ticket_id)
-> 0.0398s
-- rename_column(:ticket_article_flags, :ticket_articles_id, :ticket_article_id)
-> 0.0025s
-- add_foreign_key(:users, :organizations)
-> 0.0531s
-- add_foreign_key(:users, :users, {:column=>:created_by_id})
-> 0.0015s
-- add_foreign_key(:users, :users, {:column=>:updated_by_id})
-> 0.0009s
-- add_foreign_key(:signatures, :users, {:column=>:created_by_id})
-> 0.0033s
-- add_foreign_key(:signatures, :users, {:column=>:updated_by_id})
-> 0.0008s
-- add_foreign_key(:email_addresses, :users, {:column=>:created_by_id})
-> 0.0009s
-- add_foreign_key(:email_addresses, :users, {:column=>:updated_by_id})
-> 0.0008s
-- add_foreign_key(:groups, :signatures)
-> 0.0023s
-- add_foreign_key(:groups, :email_addresses)
-> 0.0008s
-- add_foreign_key(:groups, :users, {:column=>:created_by_id})
-> 0.0008s
-- add_foreign_key(:groups, :users, {:column=>:updated_by_id})
-> 0.0008s
-- add_foreign_key(:roles, :users, {:column=>:created_by_id})
-> 0.0010s
-- add_foreign_key(:roles, :users, {:column=>:updated_by_id})
-> 0.0048s
-- add_foreign_key(:organizations, :users, {:column=>:created_by_id})
-> 0.0008s
-- add_foreign_key(:organizations, :users, {:column=>:updated_by_id})
-> 0.0008s
-- add_foreign_key(:roles_users, :users)
-> 0.0009s
-- add_foreign_key(:roles_users, :roles)
-> 0.0007s
-- add_foreign_key(:groups_users, :users)
-> 0.0153s
-- add_foreign_key(:groups_users, :groups)
-> 0.0008s
-- add_foreign_key(:organizations_users, :users)
-> 0.0009s
-- add_foreign_key(:organizations_users, :organizations)
-> 0.0008s
-- add_foreign_key(:authorizations, :users)
-> 0.0079s
-- add_foreign_key(:translations, :users, {:column=>:created_by_id})
-> 0.1274s
-- add_foreign_key(:translations, :users, {:column=>:updated_by_id})
-> 0.0098s
-- add_foreign_key(:tokens, :users)
-> 0.0140s
-- add_foreign_key(:packages, :users, {:column=>:created_by_id})
-> 0.0033s
-- add_foreign_key(:packages, :users, {:column=>:updated_by_id})
-> 0.0008s
-- add_foreign_key(:taskbars, :users)
-> 0.0077s
-- add_foreign_key(:tags, :tag_items)
-> 0.0010s
-- add_foreign_key(:tags, :tag_objects)
-> 0.0008s
-- add_foreign_key(:tags, :users, {:column=>:created_by_id})
-> 0.0008s
-- add_foreign_key(:recent_views, :object_lookups, {:column=>:recent_view_object_id})
-> 0.0015s
-- add_foreign_key(:recent_views, :users, {:column=>:created_by_id})
-> 0.0008s
-- add_foreign_key(:activity_streams, :type_lookups, {:column=>:activity_stream_type_id})
-> 0.0015s
-- add_foreign_key(:activity_streams, :object_lookups, {:column=>:activity_stream_object_id})
-> 0.0174s
-- add_foreign_key(:activity_streams, :permissions)
-> 0.0010s
-- add_foreign_key(:activity_streams, :groups)
-> 0.0008s
-- add_foreign_key(:activity_streams, :users, {:column=>:created_by_id})
-> 0.0010s
-- add_foreign_key(:histories, :history_types)
-> 0.0030s
-- add_foreign_key(:histories, :history_objects)
-> 0.0012s
-- add_foreign_key(:histories, :history_attributes)
-> 0.0014s
-- add_foreign_key(:histories, :users, {:column=>:created_by_id})
-> 0.0010s
-- add_foreign_key(:stores, :store_objects)
-> 0.0016s
-- add_foreign_key(:stores, :store_files)
-> 0.0041s
-- add_foreign_key(:stores, :users, {:column=>:created_by_id})
-> 0.0009s
-- add_foreign_key(:avatars, :users, {:column=>:created_by_id})
-> 0.0013s
-- add_foreign_key(:avatars, :users, {:column=>:updated_by_id})
-> 0.0009s
-- add_foreign_key(:online_notifications, :users, {:column=>:created_by_id})
-> 0.0010s
-- add_foreign_key(:online_notifications, :users, {:column=>:updated_by_id})
-> 0.0008s
-- add_foreign_key(:schedulers, :users, {:column=>:created_by_id})
-> 0.0010s
-- add_foreign_key(:schedulers, :users, {:column=>:updated_by_id})
-> 0.0009s
-- add_foreign_key(:calendars, :users, {:column=>:created_by_id})
-> 0.0102s
-- add_foreign_key(:calendars, :users, {:column=>:updated_by_id})
-> 0.0008s
-- add_foreign_key(:user_devices, :users)
-> 0.0014s
-- add_foreign_key(:object_manager_attributes, :object_lookups)
-> 0.0170s
-- add_foreign_key(:object_manager_attributes, :users, {:column=>:created_by_id})
-> 0.0010s
-- add_foreign_key(:object_manager_attributes, :users, {:column=>:updated_by_id})
-> 0.0009s
-- add_foreign_key(:cti_caller_ids, :users)
-> 0.0015s
-- add_foreign_key(:stats_stores, :users, {:column=>:created_by_id})
-> 0.0127s
-- add_foreign_key(:http_logs, :users, {:column=>:created_by_id})
-> 0.0010s
-- add_foreign_key(:http_logs, :users, {:column=>:updated_by_id})
-> 0.0008s
-- add_foreign_key(:ticket_state_types, :users, {:column=>:created_by_id})
-> 0.0009s
-- add_foreign_key(:ticket_state_types, :users, {:column=>:updated_by_id})
-> 0.0009s
-- add_foreign_key(:ticket_states, :ticket_state_types, {:column=>:state_type_id})
-> 0.0008s
-- add_foreign_key(:ticket_states, :users, {:column=>:created_by_id})
-> 0.0009s
-- add_foreign_key(:ticket_states, :users, {:column=>:updated_by_id})
-> 0.0009s
-- add_foreign_key(:ticket_priorities, :users, {:column=>:created_by_id})
-> 0.0036s
-- add_foreign_key(:ticket_priorities, :users, {:column=>:updated_by_id})
-> 0.0009s
-- add_foreign_key(:tickets, :groups)
-> 0.0153s
-- add_foreign_key(:tickets, :users, {:column=>:owner_id})
-> 0.0010s
-- add_foreign_key(:tickets, :users, {:column=>:customer_id})
-> 0.0009s
-- add_foreign_key(:tickets, :ticket_priorities, {:column=>:priority_id})
-> 0.0008s
-- add_foreign_key(:tickets, :ticket_states, {:column=>:state_id})
-> 0.0008s
-- add_foreign_key(:tickets, :organizations)
-> 0.0013s
-- add_foreign_key(:tickets, :users, {:column=>:created_by_id})
-> 0.0009s
-- add_foreign_key(:tickets, :users, {:column=>:updated_by_id})
-> 0.0010s
-- add_foreign_key(:ticket_flags, :tickets, {:column=>:ticket_id})
-> 0.0010s
-- add_foreign_key(:ticket_flags, :users, {:column=>:created_by_id})
-> 0.0008s
-- add_foreign_key(:ticket_article_types, :users, {:column=>:created_by_id})
-> 0.0009s
-- add_foreign_key(:ticket_article_types, :users, {:column=>:updated_by_id})
-> 0.0009s
-- add_foreign_key(:ticket_article_senders, :users, {:column=>:created_by_id})
-> 0.0013s
-- add_foreign_key(:ticket_article_senders, :users, {:column=>:updated_by_id})
-> 0.0009s
-- add_foreign_key(:ticket_articles, :tickets)
-> 0.0013s
-- add_foreign_key(:ticket_articles, :ticket_article_types, {:column=>:type_id})
-> 0.0008s
-- add_foreign_key(:ticket_articles, :ticket_article_senders, {:column=>:sender_id})
-> 0.0007s
-- add_foreign_key(:ticket_articles, :users, {:column=>:created_by_id})
-> 0.0009s
-- add_foreign_key(:ticket_articles, :users, {:column=>:updated_by_id})
-> 0.0009s
-- add_foreign_key(:ticket_articles, :users, {:column=>:origin_by_id})
-> 0.0009s
-- add_foreign_key(:ticket_article_flags, :ticket_articles, {:column=>:ticket_article_id})
-> 0.0009s
-- add_foreign_key(:ticket_article_flags, :users, {:column=>:created_by_id})
-> 0.0009s
-- add_foreign_key(:ticket_time_accountings, :tickets)
-> 0.0011s
-- add_foreign_key(:ticket_time_accountings, :ticket_articles)
-> 0.0008s
-- add_foreign_key(:ticket_time_accountings, :users, {:column=>:created_by_id})
-> 0.0008s
-- add_foreign_key(:overviews, :users, {:column=>:created_by_id})
-> 0.0014s
-- add_foreign_key(:overviews, :users, {:column=>:updated_by_id})
-> 0.0009s
-- add_foreign_key(:overviews_roles, :overviews)
-> 0.0222s
-- add_foreign_key(:overviews_roles, :roles)
-> 0.0008s
-- add_foreign_key(:overviews_users, :overviews)
-> 0.0008s
-- add_foreign_key(:overviews_users, :users)
-> 0.0009s
-- add_foreign_key(:overviews_groups, :overviews)
-> 0.0010s
-- add_foreign_key(:overviews_groups, :groups)
-> 0.0008s
-- add_foreign_key(:triggers, :users, {:column=>:created_by_id})
-> 0.0016s
-- add_foreign_key(:triggers, :users, {:column=>:updated_by_id})
-> 0.0010s
-- add_foreign_key(:jobs, :users, {:column=>:created_by_id})
-> 0.0010s
-- add_foreign_key(:jobs, :users, {:column=>:updated_by_id})
-> 0.0010s
-- add_foreign_key(:links, :link_types)
-> 0.0010s
-- add_foreign_key(:postmaster_filters, :users, {:column=>:created_by_id})
-> 0.0010s
-- add_foreign_key(:postmaster_filters, :users, {:column=>:updated_by_id})
-> 0.0009s
-- add_foreign_key(:text_modules, :users)
-> 0.0014s
-- add_foreign_key(:text_modules, :users, {:column=>:created_by_id})
-> 0.0010s
-- add_foreign_key(:text_modules, :users, {:column=>:updated_by_id})
-> 0.0010s
-- add_foreign_key(:text_modules_groups, :text_modules)
-> 0.0009s
-- add_foreign_key(:text_modules_groups, :groups)
-> 0.0007s
-- add_foreign_key(:templates, :users)
-> 0.0010s
-- add_foreign_key(:templates, :users, {:column=>:created_by_id})
-> 0.0009s
-- add_foreign_key(:templates, :users, {:column=>:updated_by_id})
-> 0.0009s
-- add_foreign_key(:templates_groups, :templates)
-> 0.0008s
-- add_foreign_key(:templates_groups, :groups)
-> 0.0007s
-- add_foreign_key(:channels, :groups)
-> 0.0009s
-- add_foreign_key(:channels, :users, {:column=>:created_by_id})
-> 0.0009s
-- add_foreign_key(:channels, :users, {:column=>:updated_by_id})
-> 0.0009s
-- add_foreign_key(:slas, :users, {:column=>:created_by_id})
-> 0.0010s
-- add_foreign_key(:slas, :users, {:column=>:updated_by_id})
-> 0.0009s
-- add_foreign_key(:macros, :users, {:column=>:created_by_id})
-> 0.0013s
-- add_foreign_key(:macros, :users, {:column=>:updated_by_id})
-> 0.0009s
-- add_foreign_key(:chats, :users, {:column=>:created_by_id})
-> 0.0013s
-- add_foreign_key(:chats, :users, {:column=>:updated_by_id})
-> 0.0009s
-- add_foreign_key(:chat_topics, :users, {:column=>:created_by_id})
-> 0.0010s
-- add_foreign_key(:chat_topics, :users, {:column=>:updated_by_id})
-> 0.0009s
-- add_foreign_key(:chat_sessions, :chats)
-> 0.0009s
-- add_foreign_key(:chat_sessions, :users)
-> 0.0009s
-- add_foreign_key(:chat_sessions, :users, {:column=>:created_by_id})
-> 0.0009s
-- add_foreign_key(:chat_sessions, :users, {:column=>:updated_by_id})
-> 0.0009s
-- add_foreign_key(:chat_messages, :chat_sessions)
-> 0.0061s
-- add_foreign_key(:chat_messages, :users, {:column=>:created_by_id})
-> 0.0010s
-- add_foreign_key(:chat_agents, :users, {:column=>:created_by_id})
-> 0.0011s
-- add_foreign_key(:chat_agents, :users, {:column=>:updated_by_id})
-> 0.0009s
-- add_foreign_key(:report_profiles, :users, {:column=>:created_by_id})
-> 0.0014s
-- add_foreign_key(:report_profiles, :users, {:column=>:updated_by_id})
-> 0.0009s
-- add_foreign_key(:karma_users, :users)
-> 0.0010s
-- add_foreign_key(:karma_activity_logs, :users)
-> 0.0011s
-- add_foreign_key(:karma_activity_logs, :karma_activities, {:column=>:activity_id})
-> 0.0008s
== 20170531144425 ForeignKeys: migrated (0.5257s) =============================

== 20170608151442 EnhancedPermissions: migrating ==============================
-- change_column_null(:groups_users, :user_id, false)
-> 0.0004s
-- change_column_null(:groups_users, :group_id, false)
-> 0.0044s
-- add_column(:groups_users, :access, :string, {:limit=>50, :null=>false, :default=>"full"})
-> 0.1301s
-- add_index(:groups_users, [:access])
-> 0.0098s
-- create_table(:roles_groups, {:id=>false})
-> 0.0009s
-- add_index(:roles_groups, [:role_id])
-> 0.0021s
-- add_index(:roles_groups, [:group_id])
-> 0.0025s
-- add_index(:roles_groups, [:access])
-> 0.0020s
== 20170608151442 EnhancedPermissions: migrated (0.1638s) =====================

== 20170619000001 TreeSelect: migrating =======================================
-- change_column(:object_manager_attributes, :data_option, :text, {:limit=>819201, :null=>true})
-> 0.0036s
-- change_column(:object_manager_attributes, :data_option_new, :text, {:limit=>819201, :null=>true})
-> 0.0003s
== 20170619000001 TreeSelect: migrated (0.0046s) ==============================

== 20170626000001 LocaleAddDirection: migrating ===============================
-- add_column(:locales, :dir, :string, {:limit=>9, :null=>false, :default=>"ltr"})
-> 0.0055s
== 20170626000001 LocaleAddDirection: migrated (0.0061s) ======================

== 20170628000001 FormGroupSelection: migrating ===============================
== 20170628000001 FormGroupSelection: migrated (0.0884s) ======================

== 20170713000001 OmniauthOffice365Setting: migrating =========================
== 20170713000001 OmniauthOffice365Setting: migrated (0.0866s) ================

== 20170713000002 TicketZoomSetting2: migrating ===============================
== 20170713000002 TicketZoomSetting2: migrated (0.0652s) ======================

== 20170714000001 ObjectManagerUserEmailOptional: migrating ===================
== 20170714000001 ObjectManagerUserEmailOptional: migrated (0.1204s) ==========

== 20170714000002 UserEmailMultipleUse: migrating =============================
== 20170714000002 UserEmailMultipleUse: migrated (0.0131s) ====================

== 20170714000003 CleanupCtiLog: migrating ====================================
== 20170714000003 CleanupCtiLog: migrated (0.0209s) ===========================

Greetings
Stephan

@thorsteneckel
Copy link
Contributor

I can't spot any errors on that except that they were not executed. Could you please retry using Zammad now?

@thorsteneckel thorsteneckel reopened this Jul 18, 2017
@ruebenmaster
Copy link
Author

Hallo,
i try to connect with browser, no chance... not on port 3000 and not with /zammad.

GRRR....

greetings
Stephan

@thorsteneckel
Copy link
Contributor

Can you please re-run sudo systemctl restart zammad, retry and provide the current state of the log directory if Zammad is still not available?

@ruebenmaster
Copy link
Author

I done so. the status is "running"...

[root@zammad ~]# systemctl status zammad
● zammad.service
Loaded: loaded (/etc/systemd/system/zammad.service; enabled; vendor preset: disabled)
Active: active (running) since Di 2017-07-18 14:08:04 CEST; 2s ago
Main PID: 11030 (sleep)
CGroup: /system.slice/zammad.service
└─11030 /bin/sleep infinity

Jul 18 14:08:04 zammad systemd[1]: Stopping zammad.service...
Jul 18 14:08:04 zammad systemd[1]: Started zammad.service.
Jul 18 14:08:04 zammad systemd[1]: Starting zammad.service...

@ruebenmaster
Copy link
Author

ruebenmaster commented Jul 18, 2017

additional infos:

[root@zammad ~]# systemctl status nginx
● nginx.service - The nginx HTTP and reverse proxy server
Loaded: loaded (/usr/lib/systemd/system/nginx.service; enabled; vendor preset: disabled)
Active: active (running) since Di 2017-07-18 12:51:49 CEST; 1h 16min ago
Process: 2455 ExecStart=/usr/sbin/nginx (code=exited, status=0/SUCCESS)
Process: 931 ExecStartPre=/usr/sbin/nginx -t (code=exited, status=0/SUCCESS)
Process: 924 ExecStartPre=/usr/bin/rm -f /run/nginx.pid (code=exited, status=0/SUCCESS)
Main PID: 2467 (nginx)
CGroup: /system.slice/nginx.service
├─2467 nginx: master process /usr/sbin/nginx
├─2471 nginx: worker process
└─2472 nginx: worker process

[root@zammad ~]# netstat -tulpen
Aktive Internetverbindungen (Nur Server)
Proto Recv-Q Send-Q Local Address Foreign Address State Benutzer Inode PID/Program name
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 0 20148 2467/nginx: master
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 19032 921/sshd
tcp 0 0 127.0.0.1:3000 0.0.0.0:* LISTEN 995 36988 11034/puma 3.6.0 (t
tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN 26 18321 1137/postgres
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 0 19888 2062/master
tcp 0 0 127.0.0.1:6042 0.0.0.0:* LISTEN 995 36987 11032/script/websoc
tcp6 0 0 :::80 :::* LISTEN 0 20149 2467/nginx: master
tcp6 0 0 ::1:5432 :::* LISTEN 26 18320 1137/postgres
tcp6 0 0 ::1:25 :::* LISTEN 0 19889 2062/master

@thorsteneckel
Copy link
Contributor

Can you please provide the current content of the log directory? After the execution of the missing database migrations there might be some more insights.

@ruebenmaster
Copy link
Author

i attached it on first post as zammad.zip...
here again the folder /var/log/zammad
zammad.zip

@thorsteneckel
Copy link
Contributor

Please note that this is not the newest version available. The last entry in the log has the timestamp 13:53. My first reply was at 13:59. Please provide a current version as stated in my last two comments. Thanks.

@ruebenmaster
Copy link
Author

ok, doing again... ;o)
zammad.zip

@thorsteneckel
Copy link
Contributor

Thanks! That looks much better now. It looks so good, that there is no new error in there :) Could you please ensure to run the command sudo systemctl restart zammad again and check your connection? Thanks!

@ruebenmaster
Copy link
Author

one moment please... ;o)

@ruebenmaster
Copy link
Author

Hallo Thorsten,
no chance. i'm able to reach the nginx testpage, not more... not on port 3000, not on folder /zammad, not on http and not on https...

Greetings
Stephan

@ruebenmaster
Copy link
Author

[root@zammad ~]# systemctl status zammad
● zammad.service
Loaded: loaded (/etc/systemd/system/zammad.service; enabled; vendor preset: disabled)
Active: active (running) since Di 2017-07-18 14:36:56 CEST; 11s ago
Main PID: 11267 (sleep)
CGroup: /system.slice/zammad.service
└─11267 /bin/sleep infinity

Jul 18 14:36:56 zammad systemd[1]: Started zammad.service.
Jul 18 14:36:56 zammad systemd[1]: Starting zammad.service...

@ruebenmaster
Copy link
Author

ruebenmaster commented Jul 18, 2017

Only for information:
:o(
On opensuse 42.2, there is also no function after update... if i try to browse:

502 Bad Gateway
nginx/1.12.0

Why it is so difficult to update zammad?
Oh no..... But let's see CentOS7 again.

@martini
Copy link
Collaborator

martini commented Jul 18, 2017

i try to connect with browser, no chance... not on port 3000 and not with /zammad.

For security reasons with Zammad 1.6 and higher we changed the bindings from 0.0.0.0:3000 - it's only bound on localhost:3000 now. So you can't connect through network to application server on port 3000 anymore.

You have two possibilities:

  1. Use nginx as reverse proxy (e. g. with ssl termination)

  2. Bind on 0.0.0.0:3000 again (see https://docs.zammad.org/en/latest/appendix-configure-env-vars.html#configure-ip)

To verify if this is your issue use "netstat -tan|grep 3000"

@ruebenmaster
Copy link
Author

Hallo Martin,
here the result:
tcp 0 0 127.0.0.1:3000 0.0.0.0:* LISTEN

But why change the nginx configuration? It makes no sense for me, to block external connect to a helpdesk. Who should work with a system, that isn't reachable over network?

I try your docs now...

Greetings
Stephan

@ruebenmaster
Copy link
Author

Hallo Martin,
it works now. Do i have to do this every update? I'm going to write this into my documentation.

If i try to use certificates is there a doc how to configure this with zammad and nginx?

Greetings
Stephan

@martini
Copy link
Collaborator

martini commented Jul 18, 2017

Hi Stephan,

But why change the nginx configuration? It makes no sense for me, to block external connect to a helpdesk. Who should work with a system, that isn't reachable over network?

The nginx config has not changed. It's still working if you use nginx on localhost and proxy app requests to localhost:3000.

-Martin

@martini
Copy link
Collaborator

martini commented Jul 18, 2017

it works now. Do i have to do this every update? I'm going to write this into my documentation.

No. Application binding will keep on localhost. If you changed it via https://docs.zammad.org/en/latest/appendix-configure-env-vars.html#configure-ip then it is persistent (will keep on reboot and on Zammad update).

If i try to use certificates is there a doc how to configure this with zammad and nginx?

You can use certificates with nginx as usual with any other nginx setups. An example config is here https://github.com/zammad/zammad/blob/develop/contrib/nginx/zammad_ssl.conf but you also can search the internet for normal nginx+ssl howtos. Good look! 🤡 I'm sure you willing got to live nginx! 😁

@martini
Copy link
Collaborator

martini commented Jul 18, 2017

PS: Your avatar is really good! 👍

@ruebenmaster
Copy link
Author

ruebenmaster commented Jul 18, 2017 via email

@martini martini self-assigned this Jul 18, 2017
@martini
Copy link
Collaborator

martini commented Jul 18, 2017

notice you, how it works... ;o)

Wunderfull!

@martini
Copy link
Collaborator

martini commented Jul 19, 2017

JFI: Reopen if needed. Thanks a lot!

@martini martini closed this as completed Jul 19, 2017
@ruebenmaster
Copy link
Author

Hallo People,
i'm down with my nervs. :O)

Now i try to update my production server zammad. And what do i read?

"Paket zammad-1.6.1-1500902763.dab9fe99.centos7.x86_64.rpm ist nicht unterschrieben"

What is this? Is there a way to update the server without problems... It is very difficult now, to stopp my boss choosing another ticket system...

Greetings
ruebenmaster

@martini
Copy link
Collaborator

martini commented Jul 25, 2017

@monotek

"Paket zammad-1.6.1-1500902763.dab9fe99.centos7.x86_64.rpm ist nicht unterschrieben"

Any ideas about that? It's RPM on centos7.

@ruebenmaster We use https://packager.io for building packages. So we have basically no influence here.

Anyway, I recommend to have a test system anyway.

@ruebenmaster
Copy link
Author

ruebenmaster commented Jul 25, 2017

I have decide to install all new... But i have it installed correctly the way it is written on zammad.org. I don't know why there are a lot of problems with updating zammad on CentOS 7 and openSUSE 42.2. Maybe i have to use ubuntu. :O)))

packager.io, please not more to configurate... :O) There is no time for more.

greetings
ruebenmaster

@ruebenmaster
Copy link
Author

Ok, people...
a new CentOS 7, all new... Installing zammd:

"Paket zammad-1.5.0-1500965473.2be861e2.centos7.x86_64.rpm ist nicht unterschrieben"

anybody a idea?

Sorry Martin, i haven't time for troubleshooting by new installation.

greetings
ruebenmaster

@martini
Copy link
Collaborator

martini commented Jul 25, 2017

Sorry Martin, i haven't time for troubleshooting by new installation.

I'll try it by my self... I never have had issue here before.

@ruebenmaster
Copy link
Author

ruebenmaster commented Jul 25, 2017

what should i say?
new CentOS 7 ( no other applications installed )
installation exactly like docu on zammad.org... (without elasticsearch)
and:
Paket zammad-1.5.0-1500965473.2be861e2.centos7.x86_64.rpm ist nicht unterschrieben

Another question is, why is the version 1.5.0? on testing system we are at 1.6.1...

?

@monotek
Copy link
Member

monotek commented Jul 25, 2017

1.) Seems to be packager.io related.
Please try:

2.) Seems you used the develop packages before and now the stable packages.

@martini
Copy link
Collaborator

martini commented Jul 25, 2017

1.) Seems to be packager.io related.
Please try:

I can confirm that. @ruebenmaster you are right, with old repo file the "not signed" messages appears.

With new repo file (as @monotek wrote) it's working fine. Just updating the documentation right now....

@ruebenmaster
Copy link
Author

Hallo monotek,
it works? Thank you very much.
You have to correct the documentation in zammad.org with Cent OS 7. If you following the instructions there, you seemingly get the develop packages...

Greetings
ruebenmaster

@monotek
Copy link
Member

monotek commented Jul 25, 2017

@monotek monotek reopened this Jul 25, 2017
@monotek monotek closed this as completed Jul 25, 2017
@martini
Copy link
Collaborator

martini commented Jul 25, 2017

@monotek thanks

PS: It's also needed here https://docs.zammad.org/en/latest/install-update.html#update-with-rpm and https://docs.zammad.org/en/latest/install-update.html#update-with-deb right?

And centos7 has only curl on minimal installation (no wget).

@ruebenmaster
Copy link
Author

Thx.
On documantation the zammad.conf for nginx is under: /etc/nginx/sites-enabled/zammad.conf

On real life it is under:
/etc/nginx/conf.d/zammad.conf
/opt/zammad/contrib/apache2/zammad.conf
/opt/zammad/contrib/nginx/zammad.conf

i used /etc/nginx/conf.d/zammad.conf. right?

Thanks for your help.

Greetings
Stephan, the ruebenmaster

@monotek
Copy link
Member

monotek commented Jul 25, 2017

@shabo666
Copy link

Hello,
I have the the problem that zammad is only reachable on the local machine.
I tryed the above steps, but its not working for me.

Zammad is running on CentOS7
Today i updated it with:
yum -y update zammad
everything went fine but after the update, i can't reach zammad on http://10.10.2.39:300
so i searched for a solution and i found this on github.

I tried to reach zammad from the ticket server machine and its still working.

So i tried the above solution:

zammad config:set ZAMMAD_BIND_IP=0.0.0.0
systemctl restart zammad
zammad config:set ZAMMAD_RAILS_PORT=3000
zammad config:set ZAMMAD_WEBSOCKET_PORT=6042
systemctl restart zammad

But the problem persists.
with netstat -tan|grep 3000
i get this:
tcp 0 0 0.0.0.0:3000 0.0.0.0:* LISTEN

Can someone help me to get it running again?

greetings

@monotek
Copy link
Member

monotek commented Oct 24, 2017

Port seems open so it could be an firewall issue.

Nevertheless i suggest to not use 0.0.0.0 and configure nginx to proxy port 80 to port 3000 as it's more secure. Using 0.0.0.0 means https configuration could be bypassed.

@shabo666
Copy link

I checked the Firewall. Can't see anything. Everything seems to be allright.
Is there an manual for configuring nginx to proxy port 80 to 3000?

@shabo666
Copy link

i got it.
It was the internal firewall on centOS
systemctl stop firewalld
But i don't know why it was blocking zammad after the Update.

@monotek
Copy link
Member

monotek commented Oct 25, 2017

Yes, there is an example nginx config in: https://github.com/zammad/zammad/blob/develop/contrib/nginx/zammad.conf

Should be enabled by default when you installed via deb or rpm package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants